dbt Model Duration Spike Root Cause Through Okta Workflows
warningWhen 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.
Monitor for dbt model duration anomalies correlated with Okta Workflows executions that depend on those models. Track when dbt.model.execution.duration increases but dbt.model.query.duration stays stable, suggesting downstream identity operation delays. Alert when okta.workflows.execution triggered by dbt events show elevated latency.
Use dbt Cloud metadata to identify which models are taking longer. Cross-reference with Okta Workflows Execution Log to see if identity provisioning or access control flows are delayed. Check if increased data volume in dbt models is triggering more Okta operations than expected. Optimize dbt models to reduce downstream Okta API calls or batch identity operations where possible.