Argo CD Notifications and Slack: Filtering Transient Health States

Managing alert volume in a large-scale Argo CD deployment requires balancing visibility with notification noise. The Argo CD Notifications controller allows for trigger definitions based on application status changes, but default configurations often emit redundant messages during the reconciliation process.

The goal is to ensure that notifications are only dispatched for terminal or actionable states, specifically avoiding alerts while an application is in a Progressing health state during a standard sync operation. This requires a precise configuration of the when clause within the trigger definition to differentiate between a legitimate failure and a transient state change.

• How should the when expression be structured to suppress notifications during the Progressing state while still capturing a transition to Degraded?
• What is the recommended approach for ensuring that a final Synced notification is sent only after a period of instability, rather than for every minor reconciliation loop?