Services
Every service tracked by the Reporter, ranked by cost. Each row reports the service's volume and share of the total bill.
Example
"rank services by cost, 7d"
4 services account for 80% of $60K/wk: payments-svc $24K · cart-svc $18K · checkout-svc $11K · ad-svc $7K. 11 more below 5%. Top 3 services = 88% of volume.
More to ask
- "top services by volume, 30d"
- "services we're monitoring"
- "services in
stagingenv, last hour"
Prerequisites
This tool requires the Reporter deployed.
Tool schema (advanced)
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
timeRange |
string | no | 7d |
One of: 15m, 1h, 6h, 1d, 7d, 30d. Sub-day values for incident-window ranking. |
analyzerCost |
number | no | from profile | log analyzer ingestion cost in $/GB. Auto-detected if omitted. |
environment |
string | no | — | Environment nickname (multi-env setups). |
Top-N coverage line. A Top 3 services = N% of volume line appears below the per-service table. Tells the agent whether a drill-down on the top few captures the question or whether the long tail matters.
Structured next-actions block. A trailing single-line HTML comment (<!-- NEXT_ACTIONS:[...] -->) lists the recommended next tool calls as {tool, args, reason} entries. Programmatic callers extract it without regex-parsing markdown; the markdown Next actions: section above it stays human-readable.