# Data observability incident, defined with a sourced example

GLOSSARY, read 10 Nov 2026

**The short answer.** A recorded problem found by monitoring, such as late data, a failed test or a volume change. An agent can open it, read what it affects and sometimes change its status. Per the source of Sifflet's MCP server, two tools change state: close_incident_by_id and open_incident_by_id patch an incident's status.

## Definition

A recorded problem found by monitoring, such as late data, a failed test or a volume change. An agent can open it, read what it affects and sometimes change its status.

## Example from a real server

**Example.** Per the source of Sifflet's MCP server, two tools change state: close_incident_by_id and open_incident_by_id patch an incident's status.

## Related terms

- [Discovery API](/glossary/discovery-api/): The dbt platform API that returns metadata about a project's models, sources, exposures, tests and runs.
- [dynamic client registration](/glossary/dynamic-client-registration/): A step where an MCP client registers itself with an authorization server automatically, so nobody has to create a client ID by hand.
- [Cortex Analyst](/glossary/cortex-analyst/): Snowflake's natural-language analytics service.

## Where to read more

- [The directory](/)
- [All glossary terms](/glossary/)

## Sources

- github.com/siffletdata/sifflet-mcp/blob/1f390ca06d7919214bfe067991539502fdb4b9fc/src/sifflet_mcp/server.py: https://github.com/siffletdata/sifflet-mcp/blob/1f390ca06d7919214bfe067991539502fdb4b9fc/src/sifflet_mcp/server.py (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datamcpservers.com/glossary/data-observability-incident/
