OpenBrand Operations Health

Failures, monitoring coverage, and service readiness
Auth loading
Not loaded
Auto-refresh every 2 minutes
Operations summary
Loading pipeline health

Waiting for live workflow status signals.

Airflow status batches every 5 minutes.
Needs review-Not loaded
Potential delivery risk-Not loaded
Freshness risk-Not loaded
Live signal coverage-Not loaded

Workflow issues

Observed workflow conditions, not confirmed customer outages. Owners are catalog assignments.

How to investigate and escalate

Open the workflow source and recent history. Confirm customer impact and the latest observation time before escalating. A recorded owner is a catalog assignment, not a confirmed on-call responder.

For workflow failures, contact the recorded owner with the workflow ID, failed run, timestamp, source link, and customer impact. If no accountable owner is recorded, obtain an engineering incident owner before handing off.

For monitoring problems or stale observations, inspect the status publisher and its CloudWatch logs first. Missing telemetry does not prove that the underlying service is down.

CloudWatch alarms and dashboard conditions do not confirm that anyone was paged. Verify the alarm’s notification actions and the PagerDuty incident before relying on automated escalation. Use your established incident escalation channel for urgent impact.

Waiting for workflow signals.
Pipeline dependency map Explore systems and workflow routes

Pipeline Dependency Map

Idle
Link color: workflow status Solid/dashed: monitored/catalog Node color: system rollup
Airflow monitoring detail
DAG Monitor Waiting for live MWAA workflow signals.
Operator controls API target, historical as-of, refresh
All workflows and monitoring coverage Includes unmonitored catalog references

Workflow Detail

Idle
Workflow Path Role Status Signal Freshness Infra