Incidents
Incidents help you track, investigate, and resolve data quality issues when they occur. An incident is created when a data issue, such as a failed or warning check, has been confirmed and assigned to someone for resolution.
To create or update an incident, the user has to have "Manage Incidents" on the related dataset.
How to create an incident
Only users with the Manage Incidents permission for the dataset can create or edit incidents. All users with access to the dataset can view existing incidents. Read about Global and Dataset Roles
You can create an incident directly from a check result when an issue has been identified:
View incidents for a dataset
Once created, the incident will appear in the Incidents tab of the corresponding Dataset Page
It is possible to filter incidents based on lead, status, reporter, and severity.
View incidents across the organization
Incidents can also be seen in a central place in Soda Cloud. In the top navigation, click on Incidents to see all the incidents of the organization.
Use the filters and the title search to find relevant incidents.
Updating an incident
Assign a lead
Every incident requires a lead: the user responsible for resolving the issue.
Update status
Track progress by updating the incident’s status as the investigation and resolution evolve.
Add a resolution note
When marking an incident as resolved, a resolution note is mandatory to document what was done.
Include more check results
If new results are failing, you can include them in the incident.
After any changes, click Save or Resolve on the top right corner to apply them.
Integration with external systems
You can integrate incidents with Slack, MS Teams, or other external systems using Soda’s webhook capabilities or the Incidents API.
Learn on how to integrate with Soda: Integrations.
To let an AI agent investigate a failing check and publish its root cause analysis onto the incident, refer to Root cause analysis agent.
Last updated
Was this helpful?