Alerts

The Alerts page in ADOC is your central hub for tracking issues across pipelines, compute, and data reliability. An alert is automatically generated whenever a monitoring rule or policy condition is breached. These alerts allow you to catch problems early, before they impact operations, budgets, or decision-making.

By reviewing alerts, you can:

• Detect pipeline failures or performance slowdowns in real time.
• Identify data quality issues such as missing values, schema changes, or anomalies.
• Monitor compute usage and costs to avoid overruns.
• Maintain a complete audit trail of all issues across your environment.

Alerts vs Notifications

While closely related, alerts and notifications serve different purposes in ADOC:

• Alert:
  • An event created every time a rule is triggered.
  • Logged in ADOC to ensure a full audit trail.
  • Examples: A pipeline fails, sales data arrives late, or compute costs exceed budget.
• Notification:
  • The message that informs you about an alert.
  • Delivered via Slack, Teams, email, or other channels.
  • Configurable—so you can choose when and how often you’re notified.
  • Example: “Notify me only the first time a freshness policy fails.”

This separation ensures that all issues are tracked, but teams only get the right notifications at the right time, reducing noise while improving accountability.

How Alerts are Created in ADOC

You don’t create alerts directly. Alerts are automatically generated whenever a monitoring rule or policy condition is breached. This could be from:

• Policies (data quality, freshness, anomaly, drift, reconciliation)
• Pipelines (failures, SLA breaches, long runtimes)
• Compute/Budgets (cost thresholds, warehouse usage, suspend times)

Example: Creating a Data Quality Alert

1. Navigate to left main navigation menu, click Data Observability Cloud -> Governance -> Policies and click Add Policy.
2. Choose Data Quality and set up your rule (e.g., email IS NOT NULL).
3. In the Alerts & Notifications step:
   1. Pick a severity level (Critical, High, Medium, Low).
   2. Choose a Notification Group (e.g., Slack, Teams, Email).
4. Save the policy and run it. If the rule fails, ADOC creates an alert and sends a notification to your chosen channel.

Types of Alerts

ADOC generates alerts across three key domains:

• Pipeline Alerts
  • Track execution and performance of pipelines.
  • Example: Alerts for failed jobs, long runtimes, or critical errors.
• Reliability Alerts
  • Triggered by Data Reliability policies to ensure trustworthy data.
  • Example: Alerts for duplicate rows, missing values, or unusual statistical patterns.
• Compute Alerts
  • Monitor usage, health, and costs of compute environments.
  • Example: Alerts for warehouse suspends, high resource utilization, or budget threshold breaches.

Alert Lifecycle

Each alert progresses through a lifecycle, indicated by its status. Understanding these statuses helps your team coordinate effectively and maintain accountability.

Alert Lists

The Listing tab on the Alerts page provides a complete, filterable table of all alerts generated in ADOC. This is your central workspace for investigating, assigning, and managing alerts.

Finding and Filtering Alerts

The toolbar at the top of the page makes it easy to narrow down alerts and focus on what matters most:

Alerts List Details

Each row in the Alerts List represents a single alert, providing quick visibility into its context: