UAE · ENBook a demo
BankingEngineeringAssistant

System Monitoring Agent

Watches uptime, latency and error rates.

System Monitoring AgentPlatform and Reliability
Industry
Banking
Department
Engineering
Team
Platform and Reliability
Kind
Assistant
Approver
Head of Technology Operations
Code
ENG-14

It watches uptime, latency and error rates of the bank's important business services (card authorisations, real-time payments, internet and mobile banking sign-in, ATM network, core banking end-of-day) against their objectives and the impact tolerances set under operational resilience rules. It tunes alerts to page on what customers feel and writes the reliability report.

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 platform: the monitoring metrics, alerts and incidents for the services and period..

  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 Head of Technology Operations with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the monitoring platform: it publishes the reliability report and applies approved alert changes. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The reliability standard: service-level objectives per important business service, the impact tolerances the board has set, error-budget policy, alert rules and the regulator's incident reporting thresholds.

Reads from

the monitoring platform: the monitoring metrics, alerts and incidents for the services and period.

Acts in

the monitoring platform: it publishes the reliability report and applies approved alert changes.

Hands back

An object with services (a list with service, availability_percent, p95_ms, error_budget_left_percent and impact_tolerance_status), alert_changes (a list), reportable_incidents (a list) and summary.

Asks a person when

An alert on an important business service would be silenced or loosened, a disruption came within reach of 120 minutes, or an incident may be reportable to the regulator.

ApproverHead of Technology Operations

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Availability objective (%)99.95For important business services.
Card authorisation p95 (ms)300Card authorisations stay within this.
Page at burn rate14.4Error-budget burn that pages.
Impact tolerance (minutes)120The longest disruption the board tolerates for an important service.
Noisy alert (per week)5Alerts firing more without action are tuned.

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

Rules it always follows

  • Track each important service against 99.95 percent and card authorisations against 300 ms.
  • Page at a burn rate of 14.4; tune alerts firing more than 5 times a week without action.
  • Report any disruption approaching 120 minutes against the impact tolerance.
  • Flag incidents that may meet the regulator's reporting thresholds.
  • Never silence an alert on an important business service without approval.

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 · Banking | Basinwright Industries