Summary
Our users want notifications sent to them directly for operations they've triggered, e.g. "Rufus initiate a sync and gets a DM notification on Slack when the sync fails or succeeds."
Motivation
Currently, ArgoCD notifications supports a statically configured recipient list for notifications that can be configured on a per-application basis. Notification channels, e.g. #my-team-argo-notifications, become noisy. They are a good place to monitor events on a single application or group of applications, but are not a good way to get directly notified as to the status of a sync you have initiated.
A common workflow for engineers in our organization is to initiate a sync, and then to go look elsewhere, either observability dashboards or related services. If it is a low risk sync, an engineer may start on some other workstreams. If the sync fails, the engineer will either have to be monitoring their #my-team-argo-notifications channel or looking at the ArgoCD UI to see the error. Likewise, they won't know that their sync has successfully completed unless they are monitoring one of these views.
A direct notification delivered to the engineer lets them focus on the work they need and get alerted when the status of their sync changes.
Proposal
In the argocd contributor meeting, it was suggested to raise this as a feature to see if there's community interest before moving forward with a full proposal.
Summary
Our users want notifications sent to them directly for operations they've triggered, e.g. "Rufus initiate a sync and gets a DM notification on Slack when the sync fails or succeeds."
Motivation
Currently, ArgoCD notifications supports a statically configured recipient list for notifications that can be configured on a per-application basis. Notification channels, e.g.
#my-team-argo-notifications, become noisy. They are a good place to monitor events on a single application or group of applications, but are not a good way to get directly notified as to the status of a sync you have initiated.A common workflow for engineers in our organization is to initiate a sync, and then to go look elsewhere, either observability dashboards or related services. If it is a low risk sync, an engineer may start on some other workstreams. If the sync fails, the engineer will either have to be monitoring their
#my-team-argo-notificationschannel or looking at the ArgoCD UI to see the error. Likewise, they won't know that their sync has successfully completed unless they are monitoring one of these views.A direct notification delivered to the engineer lets them focus on the work they need and get alerted when the status of their sync changes.
Proposal
In the argocd contributor meeting, it was suggested to raise this as a feature to see if there's community interest before moving forward with a full proposal.