Control Tower

Data & AI Pipeline Control Tower — reliability, SLA, incidents, and quick drill-down.
AZURE_BASE is used server-side via the UI aggregator (no CORS). AWS_BASE is legacy/optional.
Open Incidents URL Open Triage URL Open Governance URL Open Policy URL Open Diagnostics URL

Overview

AZURE_BASE=(via aggregator) · AWS_BASE=legacy/optional UI API: /api/aggregate/*
Status: Idle · Last refresh:
Pipelines
Across selected source(s)
Runs (24h)
Latest end:
Failures (24h)
Failed pipelines:
SLA breaches (7d)
Total across pipelines
Stale datasets
No fresh run in 24h window
Top impacted assets
Cost (7d, AUD)
24h cost:
Cost trend
24h vs 7d daily avg
Top pipeline costs (window)
Pipeline Name Cost (AUD) Runs Source
No data available
Daily cost trend
Day Cost (AUD) Delta vs prev day Ratio vs prev day Source
No data available
Cost anomalies (latest day)
Pipeline Team / Domain Latest cost Baseline avg Ratio Z-score Severity Anomaly Action
No data available
Cost anomaly investigation
Select "Investigate" on a cost anomaly row to load related incident + triage context.
Sort:
Pipeline Team / Domain Criticality Runs 7d Fails 7d SLA (min) Breaches 7d Source
No data yet.
Tips: “Both” merges by pipeline_id. If AZURE_BASE isn’t configured, Azure results will be skipped automatically.