Data health signals preview
Data health signals offer a quick, at-a-glance view of data health when browsing your resources in dbt Explorer. They keep you informed on the status of your resource's health using the indicators Healthy, Caution, Degraded, or Unknown.
- Supported resources are models, sources, and exposures.
- For accurate health data, ensure the resource is up-to-date and had a recent job run.
- Each data health signal reflects key data health components, such as test success status, missing resource descriptions, missing tests, absence of builds in 30-day windows, and more
View data health signals for your models.Access data health signals
Access data health signals in the following places:
- In the search function or under Models, Sources, or Exposures in the Resource tab.
- For sources, the data health signal also indicates the source freshness status.
- In the Health column on each resource's details page. Hover over or click the signal to view detailed information.
- In the Health column of public models tables.
- In the DAG lineage graph. Click any node to open the node details panel where you can view it and its details.
- In Data health tiles through an embeddable iFrame and visible in your BI dashboard.
Access data health signals in multiple places in dbt Explorer.Data health signal criteria
Each resource has a health state that is determined by specific set of criteria. Select the following tabs to view the criteria for that resource type.
- Models
- Sources
- Exposures
The health state of a model is determined by the following criteria:
| Health state | Criteria |
|---|---|
| ✅ Healthy | - Built successfully in the last run AND - Built in the last 30 days AND - Model has tests configured AND - All tests passed AND - All upstream sources are fresh or freshness is not applicable (set to null) AND- Has a description |
| 🟡 Caution | - Not built in the last 30 days OR - Tests are not configured OR - Tests return warnings OR - One or more upstream sources are stale: - Has a freshness check configured - Freshness check ran in the past 30 days - Freshness check returned a warning - Missing a description |
| 🔴 Degraded | - Model failed to build OR - Model has failing tests OR - One or more upstream sources are stale: - Freshness check hasn’t run in the past 30 days - Freshness check returned an error |
| ⚪ Unknown | - Unable to determine health of resource; no job runs have processed the resource. |
The health state of a source is determined by the following criteria:
| Health state | Criteria |
|---|---|
| ✅ Healthy | - Freshness check configured AND - Freshness check passed AND - Freshness check ran in the past 30 days AND - Has a description |
| 🟡 Caution | - Freshness check returned a warning OR - Freshness check not configured OR - Freshness check not run in the past 30 days OR - Missing a description |
| 🔴 Degraded | - Freshness check returned an error |
| ⚪ Unknown | Unable to determine health of resource; no job runs have processed the resource. |
The health state of an exposure is determined by the following criteria:
| Health state | Criteria |
|---|---|
| ✅ Healthy | - Underlying sources are fresh AND - Underlying models built successfully AND - Underlying models’ tests passing AND |
| 🟡 Caution | - At least one underlying source’s freshness checks returned a warning OR - At least one underlying model was skipped OR - At least one underlying model’s tests returned a warning OR |
| 🔴 Degraded | - At least one underlying source’s freshness checks returned an error OR - At least one underlying model did not build successfully OR - At least one model’s tests returned an error |
0