Identifies models with the longest execution times that create bottlenecks in dbt job runs, enabling targeted optimization of the most impactful models.
Identifies incremental models experiencing slow merge operations due to large data volumes, inadequate clustering, or missing optimization features.
Tracks models with frequent failures or test failures to identify unstable data pipelines requiring immediate attention before they cascade to downstream dependencies.
Detects recurring database authentication or connection errors that prevent dbt from executing, often caused by expired credentials, network issues, or permission changes.
Detects increases in compilation errors related to invalid Jinja syntax, malformed YAML, or broken ref() functions that prevent dbt from building models.
Identifies upstream schema changes that break dbt models when columns are renamed, dropped, or have mismatched types, causing runtime Database Errors.
Detects issues with state:modified selection when manifest.json is overwritten prematurely, causing dbt to miss changed models in CI/CD pipelines.
Identifies test failures in CI that occur when relationships tests span modified and unmodified models, causing referential integrity checks to fail due to comparing data across dev and prod environments.
Detects merge failures in incremental models caused by duplicate unique_key values in source data, preventing proper upsert operations.
When dbt models take longer than usual and trigger Okta-managed downstream workflows, correlate dbt model execution duration with Okta Workflows execution logs to identify if bottleneck is in transformation or identity operations.
