Goal. Someone who has seen how much they used can find out where it came from.
Problem. The breakdown is a daily volume chart with By Endpoint and By SDK as separate tabs, so the four billable request types are never named as such.
Scope
- the breakdown gets its own section, with no plan limit on it, since an individual request type has no limit of its own
- rename By Endpoint to By request type. The rows are the four billable types
- a dimension menu: request type, project, environment, SDK
All four dimensions work against today's API and are built on the prototype. Project and environment cost one request per key, which a group_by would collapse into one. That is an optimisation, not a blocker.
Decide here. The menu covers the same ground as the existing tabs and the project and environment filters. If it replaces them, removing the old By SDK view and its sidebar is part of this work rather than left behind as dead code.
Done when
- the breakdown renders per dimension, and carries no limit line
- either the old tabs are gone, or there is a written reason they stayed
Goal. Someone who has seen how much they used can find out where it came from.
Problem. The breakdown is a daily volume chart with By Endpoint and By SDK as separate tabs, so the four billable request types are never named as such.
Scope
All four dimensions work against today's API and are built on the prototype. Project and environment cost one request per key, which a
group_bywould collapse into one. That is an optimisation, not a blocker.Decide here. The menu covers the same ground as the existing tabs and the project and environment filters. If it replaces them, removing the old By SDK view and its sidebar is part of this work rather than left behind as dead code.
Done when