Trust signal icons preview
Trust signal icons offer a quick, at-a-glance view of data health when browsing your resources in dbt Explorer. These icons 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 trust signal icon reflects key data health components, such as test success status, missing resource descriptions, missing tests, absence of builds in 30-day windows, and more
Access trust signal icons
Access trust signal icons in the following places:
- Search function or click on Models, Sources or Exposures under the Resource tab.
- For sources, the trust signal also indicates the source freshness status.
- View the icons under the Health column in each resource's details page. Hover over or click the trust signal to view detailed information.
- Public models tables under the Health column.
- DAG lineage graph
Trust 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
- Source collection health
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; ingestion hasn't run |
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; ingestion has not run |
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 - (TBD) Underlying models built in the last 30 days |
🟡 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 - (TBD) At least one model not built in the last 30 days |
🔴 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 |
The health state of a source collection is determined by the following criteria:
Functions as an aggregate of underlying sources
Health state | Criteria |
---|---|
✅ Healthy | - All underlying sources have freshness checks configured OR - All passed their freshness checks OR - All freshness checks ran in the past 30 days OR - All sources have a description |
🟡 Caution | - One or more sources lack freshness checks OR - One or more freshness checks returned a warning OR - One or more freshness checks not run in the past 30 days OR - One or more sources missing a description |
🔴 Degraded | - One or more underlying sources’ freshness checks returned error |