Filtering by project scopes the usage total but not the allowance, so the meter divides one project's calls by the whole organisation's limit and calls the result "% of plan consumed".
total comes from the usage query, which takes projectId. limit is max_api_calls, which is organisation-wide. Nothing on the meter says a filter is applied.
Options
- Separate the project selector from the allowance, so the meter always reports the organisation and the filter only drives the chart and the breakdown.
- Reword it for the filtered case, e.g. "Project '' contributed X% of your overall plan allowance", and make the applied filter obvious.
Either way the meter should not present a scoped numerator against an unscoped denominator without saying so.
Related to #8353, which is the same defect along a different axis: there the numerator and denominator cover different periods, here different scopes.
Done when
The meter either reports the organisation regardless of the filter, or states plainly that it is showing one project's contribution to the organisation's allowance.
Filtering by project scopes the usage total but not the allowance, so the meter divides one project's calls by the whole organisation's limit and calls the result "% of plan consumed".
totalcomes from the usage query, which takesprojectId.limitismax_api_calls, which is organisation-wide. Nothing on the meter says a filter is applied.Options
Either way the meter should not present a scoped numerator against an unscoped denominator without saying so.
Related to #8353, which is the same defect along a different axis: there the numerator and denominator cover different periods, here different scopes.
Done when
The meter either reports the organisation regardless of the filter, or states plainly that it is showing one project's contribution to the organisation's allowance.