Orchestration Monitoring
DAGs, workflows, and scheduled jobs — the layer that decides when your ETL actually runs
Jobs tracked
164
Runs (24h)
3,428
Failing jobs
27
Overdue jobs
4
Job health
Worst first. A job can be late, slow, or moving a fraction of its usual rows without a single run going red — the schedule is learned from each job's own history, not declared.
No matching results
Recent workflow runs
Newest first. A failed run raises an event into the same alert pipeline as API, ETL, and database signals.
No matching results
