Home › Key concepts › Hand-over and runbooks
Key concept · Run (advanced) · the same on every platform
Hand-over and runbooks
Leave a system the customer's team can run without you.
What it is
A runbook says how to deploy, monitor, fix common failures, update rules and roll back. Hand-over includes training, a period of shadowing, and clear ownership.
Why it matters
A forward-deployed engagement succeeds when you are no longer needed.
An example
Their on-call engineer fixes a failed connector at 2 a.m. from the runbook, without calling you.
The common mistake
Knowledge that lives only in your head.
Where you meet it on each platform
The idea stays the same; only the product name changes.
| Job | AWS | Azure | Google Cloud | Databricks | Open source |
|---|---|---|---|---|---|
| Monitoringlogs, metrics and traces, so you see trouble first | CloudWatch + X-Ray | Azure Monitor + App Insights | Cloud Logging + Trace | System tables + MLflow tracing | OpenTelemetry + Grafana |
Related ideas
Where it shows up
Part of the Run level on these paths: Forward Deployed Engineering (scale).