Watches what is live
Fabric Radar
Governed mission control for running data and ML workloads on Databricks.
Someone is watching your live workloads, and every intervention is on the record. Declared SLOs replace tribal knowledge about what healthy looks like, and a two in the morning fix becomes a governed action with an audit trail.
3 common questions, answered below ↓- Role in the family
- Watches what is live
- Databricks surfaces
- Databricks JobsLakebaseUnity CatalogTemporal
- Status
- Domain module, policies, state machines, and org-scoped projections are implemented, with a Temporal intervention worker and a Databricks effector.
- Documentation
- radar.fabric.pro
The problem
Monitoring tells you a job failed. It rarely tells you whether that breach matters, who is allowed to intervene, or what was actually done about it last time. The intervention itself usually happens in a terminal, unlogged.
How it works
Monitors carry declared service level objectives. When reality breaches one, Radar triages the anomaly and makes every intervention a governed action with a policy check and an audit record. Telemetry ingest is deliberately append-only and stays outside the governed pipeline; only state transitions pass through it.
What it does
SLOs as declarations
What 'healthy' means is written down per workload.
Governed intervention
Restarting a job or rerouting a pipeline is an action with a policy and an audit trail, not an untracked click.
Durable remediation
Interventions run as Temporal workflows, so a long remediation survives a restart mid-flight.
Anomaly triage
Detection composes the same evaluation logic.
Someone is watching your live workloads, and every intervention is on the record. Declared SLOs replace tribal knowledge about what healthy looks like, and a two in the morning fix becomes a governed action with an audit trail.
FAQ
Fabric Radar, answered
How is this different from the monitoring we already have?
Monitoring tells you a job failed. Radar carries declared service level objectives per workload, so it can tell you whether the breach matters, who is allowed to intervene, and what was actually done about it last time.
What does a governed intervention mean in practice?
Restarting a job or rerouting a pipeline runs as a policy-checked action with an audit record, executed as a durable workflow. A fix at two in the morning stops being an untracked click in a terminal.
Does it ingest all our telemetry?
Telemetry ingest is deliberately append-only and stays outside the governed pipeline. Only state transitions pass through it, which keeps the audit trail meaningful instead of drowning in events.