Acceldata
ADOC

Last updated: Nov 14, 2026 05:36 UTC

Incident Management

Incident Management provides a centralized way to configure notifications and track incidents raised by policy executions across your organization. Instead of configuring alerts separately on each policy, you create Incident Policies that define which policies or rules to monitor, what condition should raise an incident, and how you want to be notified. Every incident raised this way is tracked in a single Incidents list.

Supported entities:  Incident Management currently raises incidents for Data Reliability rules and policies only.

To access Incident Management, navigate to Operations > Incident Management in the left navigation.

Note

Incident Management works alongside the Alerts & Notifications settings that are available when you create a policy.

Incidents

The Incidents tab lists every incident raised by your Incident Policies.

Use the following controls to narrow the list:

Control

Description

Time range

Filter incidents by when they were raised. Defaults to Last 30 days.

Type

Filter by the incident's trigger type (for example, DR Policy or DR Rule).

Status

Filter by incident status (for example, Open).

Severity

Filter by severity.

Tags

Filter by the tags on the asset, policy, or rule that raised the incident. Select a Tag Scope (Asset, Policy, or Rule) and one or more tags, and then select Apply. To filter by more than one scope, select + Add another tag scope. Tags within the same scope are combined with OR, and tags in different scopes are combined with AND. For example, if you select two policy tags and one rule tag, the list shows incidents that have either of the policy tags and the rule tag.

More Filters

Access additional filter options.

Search

Search incidents by Incident ID, Name, or Source.

Columns

Show or hide columns in the incidents table.

Group Incidents By (layers icon)

Group the incidents list by Incident Policy. Each group shows the Incident Policy name and the number of incidents, and you can expand or collapse it. Select None to show the list without grouping.

The incidents table includes the following columns:

Column

Description

ID

The incident's unique identifier (for example, INC-63).

Name

The incident name, typically combining the Incident Policy name and the source.

Type

The type of entity that triggered the incident (for example, DR Policy or DR Rule).

Source

The asset or entity the underlying policy ran against.

Trigger

The condition that raised the incident (for example, Result Status: Errored).

Trigger Summary

Additional detail about what triggered the incident.

Severity

The severity assigned by the Incident Policy's condition (Critical, High, Medium, or Low).

Assignee

The user assigned to the incident. Shows Unassigned if no default assignee is configured.

Status

The incident's current status (for example, Open).

Raised On

The date and time the incident was raised.

Policy Name

The name of the policy that triggered the incident.

External Tickets

Linked external ticket references, if any.

Open For

How long the incident has remained open.

Last Fired

The date and time the underlying policy last produced this trigger condition.

External tickets

You can record the tickets in your own ticketing system that relate to an incident, such as a ServiceNow incident or a Jira issue, so your team can trace the incident to the work tracked outside ADOC. Linked tickets appear in the External Tickets column of the incidents table.

To add an external ticket to an incident:

  1. On the Incidents tab, select the incident ID to open the incident details.
  2. In the External Tickets section, select + Add.
  3. In System, select Service Now, Jira, or Other.
  4. Enter the Ticket ID, Ticket URL, and Description. All three fields are required.
  5. Select Save.

You can add more than one external ticket to an incident. To edit or delete a saved external ticket, use the edit or delete option for the ticket in the External Tickets section.

Note

An external ticket is a reference only. ADOC doesn't create, update, or synchronize the ticket in the external system.

Incident Policies

An Incident Policy defines what to monitor, the condition that raises an incident, and how notifications are sent. To create one, navigate to Incident Management > Incident Policies and select Create Policy.

Prerequisite

Select a Domain from the domain selector at the top of the page before creating an Incident Policy. The policy is scoped to the domain selected at creation time.

What do you want to monitor?

Select the entity type to monitor. Data Reliability is currently available; Pipelines, Jobs, and Data Products are shown as Coming soon.

Next, choose how to configure the policy:

  • Configure by: Rules (monitor specific rules) or Policies (monitor specific policies). An Incident Policy monitors either rules or policies. You can't combine rules and policies in one Incident Policy.
  • Global Condition or Individual Condition (see Setting conditions and severity below).

Selecting rules or policies

Select Add Rules or Add Policies to open a dialog listing the available rules or policies. Use the following controls to find what you want to monitor:

  • Policy type quick filters: Data Quality, Reconciliation, Freshness, Anomaly, Data Drift, Schema Drift, and Auto Anomaly.
  • Overall Status filter and More Filters for additional criteria.
  • Search by policy name.
  • Columns: Show or hide table columns, including Policy Type, Tags, Quality Score, Open Alerts, Overall Status, Rule Count, Records Processed, Started At, Ended At, and Total Execution.

Select the checkbox next to each rule or policy you want to monitor, then select Add Policies (or Add Rules) to confirm, or Cancel to discard your selection. Selected items appear in a list on the main page, each showing its policy type and name, with an option to remove it individually. You can return to this dialog at any time using Add Policies / Add Rules to add more.

Select by tags: Instead of selecting each rule or policy, you can define what the Incident Policy monitors by tag.

Setting conditions and severity

How you configure the trigger condition depends on whether you selected Global Condition or Individual Condition.

Global Condition applies one shared condition and severity to every selected rule or policy:

  • Condition: Choose Execution status or Result status, an operator, and one or more status values from Aborted, Errored, Successful, or Warning.
  • Severity: Critical, High, Medium, or Low.

Individual Condition lets you configure a separate condition and severity for each selected rule or policy, shown as a table with Policy (or Rule), Condition, and Severity columns — one row per item, using the same Condition and Severity options described above. Select the X on a row to remove that rule or policy from the policy.

Notification timing

Choose how you want to be notified:

Option

Description

Instant

Get notified immediately when an incident is created or retriggered.

Scheduled Summary

Receive a summary of incidents at regular intervals.

Instant + Summary

Get immediate notification plus periodic summaries.

Depending on the option selected, configure:

  • Where should we send instant notifications? — Select one or more notification channels. Shown for Instant and Instant + Summary.
  • Where should we send summary notifications? — Select one or more notification channels. Shown for Scheduled Summary and Instant + Summary.
  • When should we send summary notifications? — Set a Time zone and one or more Schedules (for example, Daily 12:00 AM). Select + Add to add additional schedules. The page displays the computed Next Execution date and time in your selected time zone. Shown for Scheduled Summary and Instant + Summary.

Regardless of the notification timing option selected, you can also turn on Also send a notification on successful runs to receive a confirmation after each successful monitored policy or rule run. Successful runs notified this way do not create an incident.

Naming and advanced settings

Enter an Incident Policy Name (required) and, optionally, select + Add description to add a description.

Expand Advanced Settings to configure:

Incident Life Cycle

  • Default assignee (optional): The user incidents are assigned to by default. Defaults to Unassigned.
  • Auto-resolve incident when conditions clear: When enabled, set the number of consecutive passing evaluations required before an open incident is automatically resolved. The incident closes as soon as the next evaluation passes the trigger threshold.

Runbook

Add one or more runbooks, each with a Runbook name, a URL, and an optional Description. Runbook links are shown in incident details and in notifications. Select + Add Runbook to add additional runbooks.

Select Create Policy to save the Incident Policy.

Manage incidents

Open an incident to review what triggered it, track the response, and keep your team informed. To open an incident, select its ID on the Incidents tab.

Update an incident

Use the controls at the top of the incident details to change the following:

  • Status: Open, Acknowledged, In Progress, Dismissed, or Resolved.
  • Severity: The severity of the incident.
  • Assignee: The user responsible for the incident.

A new incident has the status Open. Update the status as your team works on the incident, for example, Acknowledged when someone takes ownership, In Progress during the investigation, and Resolved when the issue is fixed. Select Dismissed for an incident that doesn't need action. If Auto-resolve incident when conditions clear is turned on in the Incident Policy, ADOC resolves the incident automatically when the trigger condition clears.

To discuss an incident with your team, add a comment in the Comments section, and then select Post.

Snooze an incident

Snooze an incident to silence its external notifications for a while, for example, while your team works on a known issue. In-app updates continue while the incident is snoozed.

  1. Open the incident, and then select Snooze.
  2. Select how long to snooze the incident: 1 hour, 4 hours, 24 hours, or Until resolved.
  3. Optionally, enter a reason, and then select Snooze.

The Snooze until field in the incident details shows when the snooze ends.

Activity timeline

The Activity timeline in the incident details lists the events of the incident, with the newest event first. Use it to see what happened and who acted on the incident. The timeline includes the following events:

  • Opened: The incident was raised, with its severity.
  • Notified: ADOC sent a notification. The event shows the notification kind, the channels, and the outcome.
  • Re-fired: The trigger condition occurred again. Occurrence shows how many times the incident has fired.
  • Assigned: A user assigned the incident.
  • Status changed: A user changed the status. The event shows the previous and new status.
  • Snoozed: A user snoozed the incident. The event shows who snoozed it and until when.

Manage Incident Policies

The Incident Policies tab lists your Incident Policies with their domain, type, creation and update details, and status. An Incident Policy has one of the following statuses: Draft, Active, or Paused.

To manage an Incident Policy, select the more options icon (⋮) in its row, and then select one of the following options:

  • Edit: Change what the policy monitors, its conditions and severity, its notification settings, or its advanced settings.
  • Pause: Temporarily stop the policy. The status changes to Paused. To activate the policy again, select Resume from the same menu.
  • Delete: Delete the policy.

Incident Management runs only Active policies. A Draft or Paused policy doesn't create or update incidents, even when its trigger condition occurs. When you pause or delete a policy, its open incidents stay open until a user changes their status.

What's Next

  • Configure notification channels used by Incident Policies. See Notification Integrations.
  • Review incidents raised by your policies on the Incidents tab.