> For the complete documentation index, see [llms.txt](https://docs.decube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decube.io/data-quality-v2/overview.md).

# Overview

Data Quality runs checks against your tables on a schedule, groups failures into cases, and routes alerts by rules you control.

Decube's Data Quality module tells you when a table stops behaving the way your business expects, before the people downstream find out from a dashboard. You define what good looks like for an asset, Decube checks it on your schedule, and anything that fails becomes a case your team can assign, work and close.

{% embed url="<https://www.youtube.com/watch?v=G0h-JbVbWNE>" %}

### What's in the module

| Tab          | What you do there                                                                                |
| ------------ | ------------------------------------------------------------------------------------------------ |
| **Monitors** | Define what to check and how often. Each monitor watches one asset and keeps its own run history |
| **Cases**    | Work through the failures. Incidents are grouped into cases you can assign, mute and close       |
| **Alerts**   | Write rules that route incidents to Slack, Email, Webhook and Microsoft Teams                    |

The three work as one loop: a monitor finds a problem, a case gives your team somewhere to work it, and an alert rule decides who hears about it.

### Where you can create monitors

Monitors run on assets on day 1 launch on these sources: Snowflake, Databricks, AWS Glue (with Athena), Redshift, MySQL, Microsoft Fabric and PostgreSQL. Support will expand to other sources over time.

### Start here

1. **Build your coverage.** Start with the tables your business reporting depends on.
2. **Set up an alert rule**, so a failure reaches the right team without anyone watching the module.
3. **Work the cases** as they arrive, and close them once the underlying problem is fixed.
4. **Scale up with Templates** when you move from a handful of tables to a whole schema.

{% content-ref url="/pages/0Yptu5wlTt1kOOnsxWDJ" %}
[Monitors](/data-quality-v2/monitors.md)
{% endcontent-ref %}

{% hint style="info" %}
Already running monitors in Data Quality (Classic)? See the Migration Guide for what carries over and what you recreate.
{% endhint %}