Pulumi Cloud Stack Alert Rule Suppression Windows and Deduplication

Answer

Pulumi Cloud does not have confirmed native alert suppression windows, snooze durations, or deduplication for repeated stack failures or drift events. Repeated failed pulumi up runs can generate duplicate notifications across email, Slack, PagerDuty, or webhook channels while an issue remains unresolved.

Confirmed versus likely behavior

Item	Status	Notes
Failure and drift alert rules	Confirmed	Pulumi Cloud can notify for failed stack updates and detected drift via email, Slack, PagerDuty, or webhook.
Suppression windows or snooze	Unconfirmed	No native suppression window or snooze duration is confirmed in current documentation.
Deduplication for repeated failures	Unconfirmed	Repeated failures of the same unresolved issue may produce duplicate notifications.
Role required to create or edit alert rules	Likely	Organization Admin or stack-level Admin is likely required; exact RBAC depends on the current plan.
Availability on free tier	Likely not	Alert rules and drift detection are more likely included on paid organization plans.

Steps for this case

1. Open the Pulumi Cloud console, select the organization, and open the target stack.
2. Navigate to the stack's Alerts page or Organization alert settings and review existing alert rules.
3. Attempt to create or edit a failure or drift alert rule. If a permission error appears, request Organization Admin or stack Admin access from an organization owner.
4. Check the organization's billing or plan page to confirm whether alert rules and drift detection are included on the current tier.
5. If native suppression is unavailable, avoid repeated pulumi up runs during an active incident, or route alerts through an external incident-management tool that provides its own deduplication and suppression.

Verification

• Create a test alert rule in the Pulumi Cloud console and confirm which notification channels and conditions are available.
• Run a second failed pulumi up against the same stack and observe whether a duplicate notification is delivered.
• Review current Pulumi Cloud documentation for alert rule suppression, snooze, or deduplication fields before designing incident response around them.

Missing diagnostic detail: Is your organization on a paid Pulumi Cloud plan? If alert rules are not visible in the console, tier availability is the likely cause, and the recommendation changes from configuring suppression to upgrading the plan or using external alert deduplication.