# Enable asset monitoring

The **Config** module is where you create and manage all data quality monitors. It has two tabs: **All Monitors**, which shows every monitor across your connected sources, and **Create**, where you set up new monitors.

Before creating your first monitor, make sure your data source is connected and your alert channels are configured in [Config Settings](/data-quality/config-settings.md).

{% hint style="info" %}
Grouped-By monitors are set up within each monitor type's creation flow. Schema Drift and Job Failure monitors are managed directly from the All Monitors tab.
{% endhint %}

***

## All Monitors tab <a href="#all-monitors-tab" id="all-monitors-tab"></a>

The **All Monitors** tab lists every monitor in your organisation, with its current status, last run time, and scan frequency.

<figure><img src="/files/4tNEIc92optPOsnXIvvq" alt=""><figcaption><p>All Monitors tab</p></figcaption></figure>

To manage an existing monitor, click the ellipsis (︙) at the far right of the monitor row. This opens two options:

**View Monitor** — opens the monitor configuration form, where you can modify settings, disable the monitor, or delete it.

<figure><img src="/files/VRgDL3d51VKLHCti3Tlt" alt=""><figcaption><p>Monitor configuration form</p></figcaption></figure>

<figure><img src="/files/GHiQBKRNFBitkD7CBokb" alt=""><figcaption><p>Delete monitor option</p></figcaption></figure>

**Monitor Info** — opens the monitor's history and performance data, with two tabs:

* **History** — lists each scan run with its timestamp and result status:
  * **Passed** — the scan ran and the metric was within the expected range.
  * **Failed** — the scan ran and the metric fell outside the expected range, triggering an incident.
  * **Skipped** — the scan ran but could not collect metrics, or the baseline threshold has not yet been established. See [sparse data behaviour](/data-quality/anomaly-detection-explained.md#sparse-data-and-silent-skipping).
  * **Errored** — the scan could not run. Contact <support@decube.io> if this persists.

<figure><img src="/files/LKgYRzCasD4lt5C40k7S" alt=""><figcaption><p>Monitor scan history</p></figcaption></figure>

* **Performance** — shows the monitored metric over time, alongside the confidence interval or threshold bounds.

<figure><img src="/files/ZB9HiC59P0MqllUsFtwE" alt=""><figcaption><p>Monitor performance view</p></figcaption></figure>

***

## Create tab

Navigate to **Config > Create** to set up a new monitor. Select the monitor type card that matches what you want to detect.

<figure><img src="/files/df7iQGWIvY91Y1DM6fOC" alt=""><figcaption><p>Monitor type cards in the Create tab</p></figcaption></figure>

### Available monitor types

| Monitor type                                                                                | What it detects                                              | Setup guide                                                                                                 |
| ------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------- |
| [Freshness](/data-quality/how-to-set-up-monitors/set-up-freshness-monitors.md)              | Data that has stopped arriving on its expected schedule      | [Set up Freshness monitors](/data-quality/how-to-set-up-monitors/set-up-freshness-monitors.md)              |
| [Volume](/data-quality/how-to-set-up-monitors/set-up-volume-monitors.md)                    | Row-count increments outside the expected range              | [Set up Volume monitors](/data-quality/how-to-set-up-monitors/set-up-volume-monitors.md)                    |
| [Field Health](/data-quality/how-to-set-up-monitors/set-up-field-tests.md)                  | Column-level anomalies — nulls, uniqueness, ranges, patterns | [Set up Field Health monitors](/data-quality/how-to-set-up-monitors/set-up-field-tests.md)                  |
| [Custom SQL](/data-quality/how-to-set-up-monitors/custom-sql-monitors.md)                   | Business rule violations defined by custom SQL logic         | [Set up Custom SQL monitors](/data-quality/how-to-set-up-monitors/custom-sql-monitors.md)                   |
| [Schema Drift](/data-quality/how-to-set-up-monitors/set-up-schema-drift-monitors.md)        | Table structure changes (auto-enabled)                       | [Manage Schema Drift monitors](/data-quality/how-to-set-up-monitors/set-up-schema-drift-monitors.md)        |
| [Job Failure](/data-quality/how-to-set-up-monitors/set-up-data-job-job-failure-monitors.md) | ETL pipeline job execution failures (auto-enabled)           | [Manage Job Failure monitors](/data-quality/how-to-set-up-monitors/set-up-data-job-job-failure-monitors.md) |

For a full description of each type, see [Available Monitor Types](/data-quality/available-monitor-types.md).

***

## Getting started

If you're setting up monitoring for the first time:

1. Start with [Freshness](/data-quality/how-to-set-up-monitors/set-up-freshness-monitors.md) and [Volume](/data-quality/how-to-set-up-monitors/set-up-volume-monitors.md) monitors on your most business-critical tables.
2. Add [Field Health](/data-quality/how-to-set-up-monitors/set-up-field-tests.md) monitors on key columns once the table-level monitors are in place.
3. Use [Custom SQL](/data-quality/how-to-set-up-monitors/custom-sql-monitors.md) for any validation logic that the built-in tests don't cover.

Schema Drift and Job Failure monitors are enabled automatically when you connect a data source — no setup required.


---

# 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.decube.io/data-quality/enable-asset-monitoring.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.