- Industry
- Oil & Gas
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Assistant
- Approver
- On-Call Lead
- Code
- ENG-14
It watches uptime, latency and error rates of the digital services operations depend on, such as the permit-to-work system, the historian's corporate replica, the CMMS and the fuel-card authorisation service, against their objectives. It writes the reliability report and tunes alerts, and never silences an alert on a safety-relevant service without the approver.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the monitoring system: metrics and alerts for the services..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to On-Call Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the monitoring system: it creates or updates alert rules and dashboards. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The service catalogue: objectives per service, which services are safety-relevant (permit to work, gas detection dashboards, emergency notification), alert rules and the on-call rota.
Reads from
the monitoring system: metrics and alerts for the services.
Acts in
the monitoring system: it creates or updates alert rules and dashboards.
Hands back
An object with services (availability, latency, errors, budget_left), alert_changes and incidents.
Asks a person when
A change silences or loosens an alert on a safety-relevant service.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Availability objective (%) | 99.9 | For standard services. |
| Availability for safety-relevant services (%) | 99.95 | Permit to work and emergency notification. |
| Page on burn rate | 14.4 | Error-budget burn that pages. |
| Noisy alert (fires a week) | 5 | Above this an alert is tuned. |
| Report cadence | weekly | How often. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Measure standard services against 99.9 percent and safety-relevant services against 99.95 percent.
- Page at a burn rate of 14.4.
- Tune alerts firing more than 5 times a week, but never silence one on a safety-relevant service without the On-Call Lead.
- Write the report weekly.
See the System Monitoring Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.