# Dataset dashboard

The **Dataset Page** provides a detailed view of each dataset’s health and monitoring information in Soda Cloud. It includes several tabs to help you explore and manage data quality at the dataset level.

## Checks tab

The **Checks** tab displays the **results of all checks defined in the dataset’s contract**. Checks are grouped by column, with column-level checks nested under their respective columns. **Columns with failed checks are automatically expanded** so you can spot issues quickly. You can filter the view to show only failed checks and search for specific checks or columns by name for faster navigation and troubleshooting.

> Learn more about [Data Testing](https://docs.soda.io/data-testing).

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2FzNiwUkc1HftjjbpuX6db%2Fimage.png?alt=media&#x26;token=2d9591e3-e32f-40bd-8060-bf2bcb9bc142" alt=""><figcaption></figcaption></figure>

### Filter checks by attribute

{% hint style="info" %}
Filtering check results by attribute is currently in **private preview**. Contact <support@soda.io> to enable it.
{% endhint %}

The **Checks tab** displays the results of all checks defined in the dataset's contract. **You can filter the checks** displayed on this tab by last result, column, check name, or check attribute. This lets you focus on a meaningful subset of your contract; for example, viewing only checks tagged with a specific data layer, domain, or team.

**The health score panel** **updates dynamically** to reflect only the filtered checks, showing you a pass/fail rate for that subset. A **"Results for this filter only"** label confirms the score is scoped to your current filter. You can save collections to track their progress. Note how, in the following example, the health score drops from 70% to 50% when checks are filtered by attribute:

{% columns fullWidth="true" %}
{% column %}

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2FJUmo2mhyhxTvDMA1YBwX%2Fimage.png?alt=media&#x26;token=85d95241-7153-4364-9d66-7ef1c4029191" alt=""><figcaption><p>Checks tab with no checks filter - Health score at 70%</p></figcaption></figure>
{% endcolumn %}

{% column %}

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2Ftvnq0qxNe5eH7R6LEliX%2Fimage.png?alt=media&#x26;token=b8b2f92d-7d77-4548-a0f9-6ffa0e93c934" alt=""><figcaption><p>Checks tab with checks filters - Health score at 50%</p></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

To apply a filter from the **Checks** tab:

{% stepper %}
{% step %}
Click the <i class="fa-filter">:filter:</i> filter icon

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2FgGsf8eTaPSZsp9IFYwdN%2Fimage.png?alt=media&#x26;token=aa842e91-2578-4ac2-8833-228cbf9d31c2" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Select a field from the dropdown and choose a value to filter by

<div align="left"><figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2FRjAYHpFUOoSJiAlm8bVg%2Fimage.png?alt=media&#x26;token=2405357f-e0e9-44a9-b2fb-689293bb6331" alt="" width="375"><figcaption></figcaption></figure> <figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2F5lHIc0I9YGvo7ilEz2Bf%2Fimage.png?alt=media&#x26;token=5a656908-2e7f-40ab-924e-c22a5218d51e" alt="" width="375"><figcaption></figcaption></figure></div>

You can combine multiple filters to narrow the scope further.

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2FabzJi51A59NuytUYIHpL%2Fimage.png?alt=media&#x26;token=e8e4a6e0-8fb8-4f55-afbf-0e5253b5798b" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click **Save** to save a filter as a collection
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Checks that have never been evaluated are excluded from filtered results and do not count toward the filtered health score.
{% endhint %}

## Metric Monitors tab

The **Metric Monitors** tab shows the **metrics that are actively monitored for the dataset**, helping you track trends and detect anomalies over time.

> Learn more about the [Metric Monitoring dashboard](https://docs.soda.io/data-observability/metric-monitoring-dashboard).

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2FkEnxkjWuOJdRQdHigtWD%2FScreenshot%202025-05-29%20at%205.09.51%20PM.png?alt=media&#x26;token=bae6d41c-f1dd-4232-9e4c-8486057a7d08" alt=""><figcaption></figcaption></figure>

## Columns tab - Profiling

The **Columns** tab provides an **overview of the dataset’s structure**, including column names, data types, distinct counts, and other statistics. You can search for a specific column by name to quickly locate and review its profiling details.

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2FzkPvLbPABh3XYCRRO7im%2Fimage.png?alt=media&#x26;token=6b413cf1-3af3-4c64-9974-45356c90a3b0" alt=""><figcaption></figcaption></figure>

## Scans tab

The **Scans** tab lists **all scans that have been executed for the dataset**. This gives you a dataset-level view of **what has been scanned**, **why it was scanned**, and **what the outcome was**.

Typical scan types include:

* **Contract verification** scans to validate that the dataset matches the expectations defined in its contract.
* **Metric monitoring** scans that compute and track dataset metrics over time.
* **Profiling** scans to generate profiling results for the dataset (such as statistics and distribution insights).

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2FT1UIe9wRIxzGKmxTlyQV%2Fimage.png?alt=media&#x26;token=a6883e96-6b3b-4dfd-a3b2-1d6147b0d287" alt=""><figcaption></figcaption></figure>

From the Scans tab, you can:

* **Review the list of all scans** related to the dataset.
* **Open a specific scan** to inspect its details and results.
* **Access the scan execution logs** to support troubleshooting and root-cause analysis.

## Incidents tab

The **Incidents** tab lists **incidents related to the dataset**, helping you track issues and collaborate on resolution. You can filter incidents based on criteria such as **user lead**, **status**, or **severity** to focus on the most important or urgent cases.

> Learn more about [incidents](https://docs.soda.io/manage-issues/incidents).

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2FsEZbveilg5VRMlNcQXMp%2Fimage.png?alt=media&#x26;token=cafd7acb-d8d2-4186-9690-cc9db8f3c2a1" alt=""><figcaption></figcaption></figure>

## Requests tab

The **Requests** tab displays **all contract change requests associated with the dataset**. It enables dataset owners and data consumers to collaborate on improving the dataset contract over time.

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2Fn925aiwjdL1bDkUpWwuN%2FScreenshot%202025-08-20%20at%2010.18.33%E2%80%AFAM.png?alt=media&#x26;token=40b0e157-ea50-4ad1-8759-6fd245cefffb" alt=""><figcaption></figcaption></figure>

In the **Requests** tab, you can:

* **Browse all requests** for the dataset.
* **Search and filter requests** by status (such as **Open**, **Done**, or **Won’t Do**).
* **Open a request** to review and collaborate via:
  * Messages and comments between participants
  * Proposals showing suggested contract changes (including added/modified/removed elements)

This workflow supports structured **contract collaboration** where consumers can propose changes directly, and dataset owners remain the final decision-makers for publishing updates.

<br>

***

{% if (visitor.claims.plan === 'datasetStandard')%}
{% hint style="success" %}
You are **logged in to Soda** and seeing the **Free license** documentation. Learn more about [documentation-access-and-licensing](https://docs.soda.io/reference/documentation-access-and-licensing "mention").
{% 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-and-licensing](https://docs.soda.io/reference/documentation-access-and-licensing "mention").
{% 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-and-licensing](https://docs.soda.io/reference/documentation-access-and-licensing "mention").
{% 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-and-licensing](https://docs.soda.io/reference/documentation-access-and-licensing "mention").
{% endhint %}
{% endif %}


---

# Agent Instructions: 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:

```
GET https://docs.soda.io/manage-issues/dataset-dashboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
