You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/alerting.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,4 +58,4 @@ To delete a successful delivery rate alert, select the icon in the Actions colum
58
58
> info "Deleting alerts created by other users requires Workspace Owner permissions"
59
59
> All users can delete successful delivery alerts that they created, but only those with Workspace Owner permissions can delete alerts created by other users.
60
60
61
-
Delivery Alerts are generated based on the outcomes of the last two stages in the pipeline: Failed Deliveries and Successful Deliveries. Therefore, Alerts will be determined by the attempts Segment makes to transmit events to your destination, focusing solely on events qualified for dispatch (i.e., those not discarded earlier due to business rules like protocols, destination filters, and mappings).
61
+
Segment generates delivery alerts for failed deliveries and successful deliveries, which are the last two stages of the delivery pipeline. As a result, alerts are based on Segment's attempts to send qualified events to your destination, excluding those filtered out by business rules (like protocols, destination filters, or mappings).
0 commit comments