Notification rules

Overview

Notification Rules help you manage alerts globally from one central place. Instead of configuring notifications monitor by monitor, you can create one incident notification rule that applies to a group of assets or monitors and automatically routes alerts to the right channels. This makes notifications easier to maintain, more consistent, and scalable as your monitoring grows. Additionally Incident notification rules will automatically create incidents for the failures of all the monitors applicable to them.

---

How Notification Rules Work

Each rule defines two main elements:

1. What is the rule going to cover?
2. Where should notifications be sent?

Who Can Use Notification Rules

• Admins can create, edit, and delete Notification Rules across all domains.
• Domain Editors can create, edit, and delete Notification Rules only for domains or subdomains they manage.

ℹ️

Domain Editors can only use channels, templates, and ticketing tools already configured by an Admin.

• Other roles have view-only access.

---

How to create incident notification rules

• Go to Settings → Notifications Rules.

This page shows all existing rules, their notification channels, and how many monitors they each apply to.

• Click on New notification rule

---

Step 1: Choose What the Rule Covers

Start by selecting the scope:

• One Domain or one Subdomain

Then refine the scope by:

• Selecting specific assets or filtering by monitor type (optional)

Example

You manage the Sales domain and want alerts only for payment tables.

Create a rule for:

• Domain: Sales
• Assets: payment_transactions, invoices, refunds
• Monitor types: Freshness and Volume

---

Step 2: Choose Where Notifications Go

You can send notifications to destinations already configured by your Admin.

Notification Tools

• Slack
• Microsoft Teams
• Email
• Webhook

Ticketing Tools

• Jira
• ServiceNow

Only one template per ticketing tool can be selected per rule.

ℹ️

Important information for ticketing tools

Domain editors can only use Admin-provided ticket templates, but they can edit allowed custom fields. Always send a test ticket before saving to confirm the integration, project, and fields work correctly.

Example

Send alerts for Sales monitors to:

• Slack: #finance-alerts
• Email: [email protected]
• Jira: FINOPS template

---

Step 3: Save the Rule

Once saved, the rule applies automatically to all matching monitors.

If a monitor fails:

• Notifications are sent to selected destinations
• A Sifflet Incident is created automatically (unless overridden)

This helps centralize alerting and resolution

ℹ️

Example

A freshness monitor on payment_transactions fails and matches the Finance rule:

• Slack alert sent
• Jira ticket created
• Incident created in Sifflet

---

Notification rules Logic

Using Rules with New Monitors

When creating a new monitor:

• Matching Notification Rules are applied automatically.
• You do not need to configure notifications manually.

Example

You create a new freshness monitor on refunds inside Finance. If your Finance rule already covers that asset, the monitor inherits the rule instantly.

ℹ️

Monitors created before the feature release that already had notification settings will retain their existing configuration and will appear as custom notifications.

---

Custom notifications

If needed, you can override inherited rule behavior for an individual monitor. Use this when one monitor needs special handling.

Example

Most Finance alerts go to #finance-alerts, but one critical monitor should notify executives. Enable override on that monitor and add the specific destinations.

---

How Multiple Rules Behave

A monitor can have more than one notification rule applied to it. When that happens, notification and ticketing tools behave differently.

• Notification tools (Slack, Email, Teams, Webhook) are combined across all matching rules.
• Ticketing tools (Jira, ServiceNow) use only one rule: the oldest matching rule that contains a ticketing destination.

A monitor matches two notification rules:

Example 1

Result: Notifications go to Channel 1 + Channel 2. Jira ticket is created based on Template A.

Example 2

Result: Notifications go to Channel 1 + Channel 2. Jira ticket is created based on template X.

---

Visibility

You can see what notification rules are applied in:

• Settings > Notification Rules overview (Click on the notification rules to se all the details

• Monitor Overview
• Incident Overview

This helps users understand why they received an alert.