An operations report
An anonymized example of an agent that reads one metrics source and writes a report a person can check. No account or measured result is named.
Anonymized
An example, not a named engagement
This page describes a kind of system. It does not name a client, an organisation, or a measured result.
The problem
A team already collects operational metrics. The repeated job is a short written report for one time window: what moved, and what the alarms say. The report should not require a new console, and it should not change the infrastructure.
Approach
How the work is shaped
- One agent, one metrics source, one time window
- The agent may call only the read-only tools it was given: the metrics view, the statistics, and the alarms
- It writes the report in plain language
- A dry run prints the report and does not send it
- Sending the report is a separate step a person can leave off
Architecture
How the pieces sit
- Each run starts a fresh session
- Shell and file tools are turned off
- A turn limit and a spend ceiling bound the run
- The agent inspects. It does not change the system it reads
Stack
The kind of tools
- Agent runner
- Metrics API
- Read-only tools
A similar workflow
Describe the job. These pages are examples of a build. They do not report a result.