SLA Monitoring Agent
Watches uptime, latency and error rates against client SLAs and SLOs.
- Industry
- IT Company
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Assistant
- Approver
- Head of Service Delivery
- Code
- ENG-14
It watches uptime, latency and error rates for the SaaS products and managed-services clients against each service's objectives and the availability the client's SLA promises, tracks error-budget burn, and tunes alerts so they page only on what threatens an SLA. It reports SLA attainment per client each month, with the minutes that could earn a service credit.
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 cloud monitoring and observability stack: availability, latency, error rates, alert history and maintenance windows for the services named..
- 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 Head of Service Delivery with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the ticketing and service management system: it files the monthly SLA report per client and opens tasks for alert tuning. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The reliability standards: SLOs per service, SLA availability and measurement terms per client, maintenance exclusions, alert rules and the on-call rota.
Reads from
the cloud monitoring and observability stack: availability, latency, error rates, alert history and maintenance windows for the services named.
Acts in
the ticketing and service management system: it files the monthly SLA report per client and opens tasks for alert tuning.
Hands back
A list with one entry per service, each with service, client, availability_percent, sla_target_percent, downtime_minutes, credit_threshold_crossed (true or false), budget_used_percent and alert_changes.
Asks a person when
The report shows a client SLA breached and the report goes to the client, or an alert that pages is to be silenced.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Default availability objective (%) | 99.9 | Used where no client SLA applies. |
| p95 latency objective (ms) | 500 | Latency above this counts against the objective. |
| Page at burn rate | 14.4 | Error-budget burn at or above this pages on-call. |
| Warn when SLA budget used (%) | 50 | When this share of a client's monthly SLA allowance is used, the account manager is warned. |
| Noisy alert (per week) | 5 | Alerts firing more without action are tuned. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Measure availability exactly as each client's SLA defines it, excluding only notified maintenance.
- Page on-call at a burn rate of 14.4 or more.
- Warn the account manager when a client has used 50 percent of the month's SLA allowance.
- Use 99.9 percent and 500 ms where no SLA applies.
- Tune alerts that fire more than 5 times a week without action.
- Report SLA attainment per client with the minutes counted and whether a service credit threshold was crossed.
See the SLA 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.