Managed Services
Monitoring and on call
The difference between monitoring and alerting, plus a rota that names an owner.
DEFINITION
Definition
Monitoring and on call work connects service signals to actionable alerts, a named rota, documented authority and an escalation path for incidents outside working hours.
THIS IS FOR YOU IF
- You can provide monitoring system access.
- A named owner can supply a named service owner.
- Your team needs a monitoring baseline, on call rota and incident response runbook.
HONEST FIT
Not for you if
no authorised person can be available to act when a production alert fires.
WHAT WE BUILD
The work inside the scope
Inputs from you: Monitoring system access, Recent incident examples, A named service owner and Current escalation documentation. Work items: Service signal inventory, Alert rule configuration, On call rota design, Escalation paths and Incident review records. Together they produce a monitoring baseline, on call rota and incident response runbook.
01
Service signal inventory
02
Alert rule configuration
03
On call rota design
04
Escalation paths
05
Incident review records
PRODUCES
A monitoring baseline, on call rota and incident response runbook
HOW IT GOES
A three to six weeks working range
- 01
Set the boundary
Confirm the scope, the owner and the decisions that sit inside three to six weeks.
- 02
Inspect the inputs
Your team supplies monitoring system access, recent incident examples, a named service owner, current escalation documentation.
- 03
Build the work
We complete the agreed items and keep exceptions with a named owner.
- 04
Hand over the artefact
You receive a monitoring baseline, on call rota and incident response runbook.
WHAT YOU GET
An artefact your team holds
A monitoring baseline, on call rota and incident response runbook
FAQ
Questions about Monitoring and on call
Monitoring and on call covers service signal inventory, alert rule configuration, on call rota design, escalation paths, incident review records.