API Monitoring
The invoice's view of the API layer — spend across gateways, the isolated cost of error traffic, and pricing-model waste detection.
At a glance
| Route | /api-monitoring |
| Group | Analyze |
| Page permission | intelligence |
What it is
The invoice's view of the API layer. It reports spend and trend across API Gateway, Azure API Management, Google Apigee, and Oracle Cloud's API gateway, isolates the cost of error traffic, identifies pricing-model waste, and surfaces API-specific detector findings.
Who it is for
Platform and API teams, and FinOps practitioners investigating a cost line that provider bills rarely break down usefully.
How it works
Pricing-model waste
API gateway pricing is unusually easy to get wrong
The cost model differs sharply between product tiers. REST versus HTTP APIs on AWS, for example, differ by roughly a factor of three for equivalent traffic.
The decision between tiers is usually made once at design time and never revisited against actual traffic.
The module analyses which pricing model is in use against actual traffic shape, and identifies where the wrong one is selected.
Error spend
Failed requests are billed identically to successful ones. An endpoint returning a high proportion of 4xx or 5xx responses is spending money to produce nothing — a cost line that is effectively invisible in provider billing.
Features
- Cross-provider API spend and trend across API Gateway, APIM, Apigee, and OCI
- Error spend isolation — the cost of requests that failed
- Pricing-model waste detection, identifying where a cheaper API product would serve the same traffic
- Cost efficiency analysis and a spend attribution breakdown
- API-specific detector findings routed to the opportunity pipeline
How to use it
Connect the accounts hosting API gateways
And confirm ingestion covers them.
Review total API spend and its trend
This is often materially larger than teams expect.
Examine error spend
A high figure indicates a reliability problem with a direct and quantified cost — which is usually what unblocks the engineering investment.
Review pricing-model findings
Migrating from a REST API to an HTTP API where features permit is frequently a large, low-risk saving.
Route findings into Opportunity Queue
For tracking alongside the rest of the estate.
Why it matters
API gateway cost is one of the most commonly mispriced lines in a cloud bill, because the product-tier decision is made once at design time and never revisited against real traffic.
Isolating error spend additionally gives reliability work a hard financial justification — which is often what turns "we should fix that eventually" into funded work.
Connects to
- Findings flow to Opportunity Queue
- Complements Database Health as a service-layer deep dive
- Overview data computed within Intelligence
Database Health
Deep operational monitoring for managed databases — connections, storage, latency, replication lag, query performance, forecasting, and executable auto-actions.
Kubernetes
Container cost allocation down to namespace, deployment, and team level, with rightsizing and idle-pod recommendations from measured container utilisation.