We’d like to request improvements to the billing visibility, specifically around how worker usage is calculated and billed under the P95 model.
Background:
Currently, the P95 billing model is a bit tricky to fully grasp from the UI, especially when trying to estimate how much we'll be billed or whether we’re within our buffer. We asked a few questions and got helpful answers:
Example:
If we occasionally exceed the limit (e.g., 6 workers for a short period), the P95 might still be within our contracted limit (e.g., 5 workers), meaning no extra charges.
However, if we go far over (e.g., 30 workers for the same short time), this could push the P95 up and cause overages.
So while both duration and degree of overage matter, it’s currently hard to know what our actual risk or buffer is.
Feature Request:
We’d love to see better visibility in the UI and/or via metrics endpoints around this billing model, specifically:
Current P95 usage: Where we stand right now for the billing cycle.
Projected billing impact: A clear estimate of our current or projected overages, if any.
Buffer insights: An answer to the question: “How much buffer do we have left this month?”
Simulation tool: Something that helps us simulate the impact of increasing worker count temporarily (e.g., during migrations between pools) so we can make informed decisions.
Why it matters:
This will help us:
Plan operations like migrations without unintentional overages.
Understand when it's safe to scale up temporarily.
Avoid surprises in billing.
Thanks for your consideration!
Please authenticate to join the conversation.
⬆️ Gathering votes
💡 Feature Requests
UI/UX
27 days ago
Get notified by email when there are changes.
⬆️ Gathering votes
💡 Feature Requests
UI/UX
27 days ago
Get notified by email when there are changes.