Incident Details

Explore the Incident Details page to investigate root causes, review history, and assess downstream impact.

When you select any incident from the Data Quality module, you are taken to the Incident Details page. This page gives you the full context of the incident: what triggered it, the historical trend, who owns it, and which downstream assets are at risk.

Incident Types

Decube categorises incidents into six types based on the monitor that triggered them.

Type	What triggered it	Common use case
Freshness	Data stopped updating within the expected window	Real-time dashboards and daily reports
Volume	Row count changed unexpectedly	Missing data loads or pipeline issues
Field Health	Column-level anomaly detected	Null spikes, uniqueness violations, range breaches
Schema Drift	Table structure changed	Preventing downstream application failures
Custom SQL	A custom SQL validation rule was breached	Complex business logic and data relationship checks
Job Failure	An ETL pipeline job failed	Data transformation process monitoring

Assignee & Audit History

You can assign any incident to a team member directly from the Incident Details page. Open the incident, click the Assignee field in the right panel, and select the relevant person.

All actions taken on an incident — assignments, status changes, comments — are logged automatically in the Audit History section at the bottom right of the page.

Assignee management and Audit History on the Incident Details page

Tabs

The Incident Details page is organised into tabs. Each tab surfaces a different dimension of the incident.

Details

The Details tab shows the core metadata for the incident: the affected asset, incident type, level, monitor mode, test name, and description. This is the starting point for understanding what triggered the alert and what value was observed.

Preview

The Preview tab shows a data preview of the affected table or column at the time the incident was detected.

History

The History tab lists past monitor runs for the affected asset, including the metrics from each scan. Use it to identify the run that first surfaced the anomaly and compare it against successful scans to understand what changed.

The History tab for a Field Health incident

Impacted Areas

The Impacted Areas tab generates a list of downstream assets that may be affected by the incident, based on lineage. This includes downstream tables, jobs, and dashboards. You can export the list as a CSV and share it with the owners of those assets.

Downstream assets impacted by a Custom SQL incident

Continued list of impacted assets

Lineage

The Lineage tab surfaces column-level lineage directly within the Incident Details page, so you can trace the root cause and downstream impact of an incident without leaving the incident context.

When you open the Lineage tab, Decube renders a column-level lineage graph centred on the affected asset. The graph shows the upstream sources feeding into the affected column and the downstream tables, jobs, and dashboards that depend on it. You can zoom, pan, and reset the view using the controls in the graph toolbar.

• Trace the source of bad data — follow upstream connections to identify where an anomalous value or null originated.

• Assess downstream exposure — see which tables and BI assets consume the affected column, so you can prioritise fixes by blast radius.

• Inspect related columns — each node in the graph shows the related columns for that asset, giving you the full propagation path at a glance.

The lineage graph reflects the connections Decube has detected for that asset.

Automated Lineage

Related Pages

Managing IncidentsIncident model feedback