UAE · ENBook a demo
Insure AIEngineeringAssistant

System Monitoring Agent

Watches uptime, latency and error rates.

System Monitoring AgentPlatform and Reliability
Industry
Insure AI
Department
Engineering
Team
Platform and Reliability
Kind
Assistant
Approver
On-Call Lead
Code
ENG-14

It watches uptime, latency and error rates for the insurance platforms, with the tightest targets on quote and bind, FNOL and claims payments. It reports against SLOs, tunes noisy alerts and flags when an outage may need notifying to the regulator.

How it works

6 steps, and a person signs off before step 6.

  1. 01Looks it up

    Finds the record the request is about in the monitoring system: uptime, latency, errors and alerts for the services..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  5. 05Asks a person

    Hands the work to On-Call Lead with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the monitoring system: it updates alert rules and posts the SLO report. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The SLOs by service, alert rules, the on-call rota and the regulator's incident notification rules for outsourced and critical services.

Reads from

the monitoring system: uptime, latency, errors and alerts for the services.

Acts in

the monitoring system: it updates alert rules and posts the SLO report.

Hands back

An object with services (a list, each with availability, p95_ms, error_rate and budget_left), breaches, noisy_alerts and notifiable_flags.

Asks a person when

A critical service is down for 120 minutes or an SLO is breached.

ApproverOn-Call Lead

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Availability SLO (%)99.9For quote, FNOL and claims payment.
p95 latency target (ms)1000For quote calls.
Burn rate that pages2Error budget burn that pages.
Noisy alert (fires a week)20Above this it is tuned.
Outage that may be notifiable (minutes)120A critical service down this long is flagged for the regulator check.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Report quote, FNOL and claims payment against 99.9 percent and 1000 ms.
  • Page at a burn rate of 2.
  • Tune alerts firing over 20 times a week.
  • Flag a critical service down for 120 minutes for the On-Call Lead to decide on regulator notification.
  • Never put policyholder data in alerts.

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.

System Monitoring Agent · Insure AI | Basinwright Industries