Pulumi Service Alert Configuration: Mitigating Duplicate Notifications Across Channels

Goal: Streamline Pulumi Alerts

When configuring Pulumi Service alerts, the objective is to receive actionable notifications for stack failures, drift, and provider mismatches without overwhelming teams with duplicate messages. Each alert can be routed to multiple channels—email, Slack, Teams, or webhooks—so a single event may generate several identical notifications.

Current Alert Scope

Alert rules can be scoped to individual stacks, projects, or the entire organization. Triggers include stack update failures, successes, drift detection, provider version mismatches, and custom runtime errors. The UI allows filtering by severity, resource type, and channel.

Duplicate Notification Issue

The Pulumi Service does not provide built‑in throttling or deduplication across channels. Consequently, a single stack update failure can result in simultaneous alerts in Slack, email, and a webhook, creating noise and potential alert fatigue.

How can we configure the alert system to suppress or de‑duplicate notifications when multiple channels are active? Is there an option to set per‑channel throttling or a global deduplication window? What best‑practice patterns exist for balancing timely alerts with minimal noise across the Pulumi alert ecosystem?