Reporting
One figure, and four ways to defend it.
The August total decomposed by person, team, project and application. Every view sums to the same number, because they are four readings of the same request log.
Reporting
One total, four decompositions.
The same August figure broken down by person, team, project and application. Department comes from your directory, so team reporting needs no extra configuration.
| Person | Detail | Share | Cost |
|---|---|---|---|
| M. Okonkwo | platform · eng | 10.3% | $1,904.12 |
| R. Halvorsen | payments · eng | 7.9% | $1,455.80 |
| S. Iyer | platform · eng | 6.0% | $1,101.36 |
| T. Bergström | data · eng | 5.4% | $988.04 |
| A. Cardoso | mobile · eng | 4.4% | $812.55 |
| J. Whitfield | payments · eng | 3.8% | $704.19 |
| 142 others | — | 62.2% | $11,436.60 |
| Total | 100.0% | $18,402.66 |
Where each dimension comes from
Person
The key the request arrived on, issued to a named person.
Team
Department from your directory, via Entra ID or Google Workspace. No extra configuration.
Project
A header the client sets. Untagged traffic is shown as untagged rather than guessed.
Application
The application key, including service accounts and per-end-user traffic behind one key.
It reconciles with the bill
Cost is computed per request from the model, the region and the token counts Bedrock returned, so the total lines up with the Bedrock line on your AWS bill.
Reporting works fully with conversation retention set to off. Usage and cost are metered from the request, not from the text.
Data & your staff →| Model | eu.anthropic.claude-sonnet-4-5 |
| Profile served by | eu-west-1 |
| Input tokens | 18,204 |
| Output tokens | 1,932 |
| Cache read | 140,880 |
| Cost | $0.0879 |