The meter shows usage as a percentage of the plan limit, but the limit and the period being viewed do not always measure the same span.
max_api_calls is allowed_30d_api_calls: a 30-day allowance.
| Period on screen |
What the percentage means |
| Last 30 days |
correct |
| Last 90 days |
roughly 3x overstated |
| Current billing period |
correct only where the term is monthly |
So on "Last 90 days" an organisation reads "55% of plan consumed" from 27.6M against 50M, when the 50M covers 30 days.
Raised on #8320, where the chart was fixed to follow the period being viewed. The meter was not.
Options
- Show the percentage only where the comparison holds, and otherwise show the total with the allowance labelled. A missing percentage is better than a wrong one.
- Pro-rata the allowance to the period, clearly marked indicative.
- Label the allowance, e.g. "50M / 30 days", and let the reader do the arithmetic.
Needs a product call rather than an engineering one, and it interacts with #8188: a projection divides by the period length, so both want the same answer about what the allowance covers.
Done when
The meter never states a percentage that compares two different spans.
The meter shows usage as a percentage of the plan limit, but the limit and the period being viewed do not always measure the same span.
max_api_callsisallowed_30d_api_calls: a 30-day allowance.So on "Last 90 days" an organisation reads "55% of plan consumed" from 27.6M against 50M, when the 50M covers 30 days.
Raised on #8320, where the chart was fixed to follow the period being viewed. The meter was not.
Options
Needs a product call rather than an engineering one, and it interacts with #8188: a projection divides by the period length, so both want the same answer about what the allowance covers.
Done when
The meter never states a percentage that compares two different spans.