You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What
Our tooling for detecting and investigating billing discrepancies is not great - it's hard to correlate information from Stripe and multiple AWS-hosted services to understand whether a user was billed incorrectly or not.
We could start to build some scripts that show a) recorded usage b) storage allocated and c) usage reported to stripe for a particular user. We could even run this on a regular basis and throw an error or something if it's too large.
Why
We are likely to have billing issues forever - some real, some a result of user error or confusion - and having a good set of tools to investigate them will save lots of time in the long run.
Cost
A basic script to pull this information together for a single user should be a day or two of work, implementation, testing, documentation, etc
The text was updated successfully, but these errors were encountered:
What
Our tooling for detecting and investigating billing discrepancies is not great - it's hard to correlate information from Stripe and multiple AWS-hosted services to understand whether a user was billed incorrectly or not.
We could start to build some scripts that show a) recorded usage b) storage allocated and c) usage reported to stripe for a particular user. We could even run this on a regular basis and throw an error or something if it's too large.
Why
We are likely to have billing issues forever - some real, some a result of user error or confusion - and having a good set of tools to investigate them will save lots of time in the long run.
Cost
A basic script to pull this information together for a single user should be a day or two of work, implementation, testing, documentation, etc
The text was updated successfully, but these errors were encountered: