> For the complete documentation index, see [llms.txt](https://docs.upriverdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.upriverdata.com/product-usage/incidents/incident-types.md).

# Incident Types

Upriver classifies the data incidents into different types so that users can immediately understand what is happening in their data.

<table><thead><tr><th width="228">Type</th><th width="259">Meaning</th><th>Examples</th></tr></thead><tbody><tr><td>Schema Incident</td><td>The schema of the data source has changed.</td><td><ul><li>Type change from string to int for a specific field.</li><li>A new field has been added/removed in the data source.</li></ul></td></tr><tr><td>Metata Incident</td><td>An anomaly was detected in either the freshness or the volume of data.</td><td><ul><li>A sharp drop in the number of items being ingested.</li><li>An anomaly in the age of data in the data source.</li></ul></td></tr><tr><td>Format Incident</td><td>The semantic format for a given field has changed or the ratio between different formats seen for the field has changed.</td><td><ul><li>Change in the distribution between URLs and IPs in a domain field.</li><li>A field receiving emails begins seeing malformed emails values.</li></ul></td></tr><tr><td>Distribution Drift</td><td>A change has been detected in the distribution of one of the measured metrics for the datasource. This can include change in the expected ranges, percentiles and so on.<br><br>These incidents can be caused either by anomalous values for a given metric or by a drift in the distribution, i.e. the expectations from the datasources have changed.</td><td><ul><li>An out of range value in a numerical column.</li><li>A shift in the expected mean value of a numerical column after multiple runs.</li></ul></td></tr><tr><td>Field Metadata Incident</td><td>An anomaly was detected in the completeness or uniqueness of a given field.</td><td><ul><li>The completeness (ratio of non-null values to null values) has changed for a specific field/column in the data.</li></ul></td></tr><tr><td>Unmet User Field Expectation</td><td>The behavior of a field does not match an expectation explicitly set by the user.</td><td><ul><li>A vlue outside of a given range defined by the user.</li><li>The completeness of a field is below the threshold the user defined.</li></ul></td></tr><tr><td>Unmet User Metadata Expectation</td><td>The volume or freshness do not match the expectation set by the user.</td><td><ul><li>The newest available data is older than a certain threshold defined.</li><li>The number items being ingested is higher than a given threshold.</li></ul></td></tr></tbody></table>

{% hint style="info" %}
Incidents groups might include more than one type of incident.\
For example, a drop in the number of rows can appear as both an "Unmet User Metadata Expectation" and as a "Metadata Expectation".
{% endhint %}

Incidents can be filtered by there type in the incident list page.

<figure><img src="https://875415170-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLE0zsJmUpeLjYw085cnO%2Fuploads%2FwAJhSzhSBbQvZTSRfT9l%2Fimage.png?alt=media&amp;token=e1634c81-bef7-4453-82ce-3676a258ffe0" alt=""><figcaption></figcaption></figure>