> For the complete documentation index, see [llms.txt](https://docs.soda.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.soda.io/manage-issues/analyze-monitor-and-check-results.md).

# Analyze monitor and check results

When you access a **monitor** (from Metric Monitoring) or a **check** (from the Contract), Soda Cloud provides a **time series view** that shows how the monitored metric or check result evolves. This helps you explore the history of data quality issues, spot trends, and understand changes in your data.

<figure><img src="/files/azkUIkBTtNlAR00ZhBNl" alt=""><figcaption></figcaption></figure>

## Diagnostics

For certain types of checks, **additional diagnostic information** is also available for check results to help you investigate issues in more detail.

For example:

* **Schema Checks**: View a side-by-side comparison of the **actual vs. expected schema** to identify differences.
* **Missing, Duplicate, or Invalid checks**: See the percentage of failed rows vs. passing rows, including a breakdown of **valid**, **missing**, **invalid**, and **duplicate** rows, as well as the **number of tested rows**, to understand the scale and impact of the issue.
* **Reconciliation checks**: View reconciliation insights from both the **source** and the **target** datasets to compare results, identify gaps, and better understand mismatches.

This view helps you drill down into specific data issues, explore context, and take informed action.

<figure><img src="/files/1cxfztuzwbognXa6kyCG" alt=""><figcaption></figcaption></figure>

***

{% if visitor.claims.plan === 'datasetStandard' %}
{% hint style="success" %}
You are **logged in to Soda** and seeing the **Dataset Standard license** documentation. Learn more about [Documentation access & licensing](/reference/documentation-access-and-licensing.md).
{% endhint %}
{% endif %}

{% if visitor.claims.plan === 'enterprise' %}
{% hint style="success" %}
You are **logged in to Soda** and seeing the **Team license** documentation. Learn more about [Documentation access & licensing](/reference/documentation-access-and-licensing.md).
{% endhint %}
{% endif %}

{% if visitor.claims.plan === 'enterpriseUserBased' %}
{% hint style="success" %}
You are **logged in to Soda** and seeing the **Enterprise license** documentation. Learn more about [Documentation access & licensing](/reference/documentation-access-and-licensing.md).
{% endhint %}
{% endif %}

{% if !(visitor.claims.plan === 'enterprise' || visitor.claims.plan === 'enterpriseUserBased' || visitor.claims.plan === 'datasetStandard') %}
{% hint style="info" %}
You are **not logged in to Soda** and are viewing the default public documentation. Learn more about [Documentation access & licensing](/reference/documentation-access-and-licensing.md).

If you do have a Soda license, make sure to **log in to Soda Cloud in this same browser**.
{% endhint %}
{% endif %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.soda.io/manage-issues/analyze-monitor-and-check-results.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.