Notification configuration

The Subscription notification configuration page lets you define notification rules that control which subscription events trigger messages, and where those messages are sent.

Each configuration groups a set of rules under a shared name and cluster type, so you can manage alerts consistently across environments.

Click Add alert notification rule to add a new configuration.

Add an alert notification rule

Define the following in the alert notification rule:

Name

Give the configuration a clear, human-friendly name (for example, Production critical alerts or Staging QA notifications). This name helps you and your team quickly identify what kind of notifications the configuration controls.

Cluster type

Choose which type of clusters this configuration applies to (for example, production or non-production). Use separate configurations for different environments when the audience, urgency, or content of notifications differs.

Channels

Select the channels where the configuration applies. See Notification channels.

Whitelisted rules

Whitelisted rules are explicitly allowed notification types for this configuration. Only events matching at least one whitelisted rule are considered for delivery.

Use whitelists when you want to focus on a subset of events, such as:

• Only deployment failures
• Only subscription lifecycle events (create, update, delete)
• Only security-relevant incidents

Blacklisted rules

Blacklisted rules are notification types that should never be sent for this configuration, even if they match the whitelist. They act as an override to silence noisy or low-value events.

Typical use cases:

• Suppress non-critical events in production (for example, routine syncs or health checks)
• Exclude high-volume events that are already covered by another monitoring system

Multiple rules and configurations

You can add multiple rules within a single configuration to capture different kinds of events for the same audience (for example, deployment failures and certificate expiry warnings going to the same team).

You can also create multiple configurations to send different notifications to different channels or teams. For example, one configuration for business stakeholders and another for on-call engineers.

Alert types

For the alert types you can whitelist or blacklist, and for runbooks when an alert fires, see Alerts and Troubleshooting alerts in DX Cloud Operations.