#louis_best-practices
fossil schoonerBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1333428131666858036
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
cerulean geyser
👋
- will the deprecated API be removed in the future ? (approx 1 year, 5, or 20)
As far as I know there is no plane to delete it yet.
With the new billing meters it's much harder since it doesn't do monthly aggregation (just daily)
What you mean by this? I'm not sure I understand this part. You can use monthly prices using the billing meters...
crude hinge
It is easy to do with a meter about api requests, or a non unique value. For MAU this is an aggregated value over a month so it's much more complicated to implement right now since you have to send stripe each day the MAU count minus the previous days' MAU count
cerulean geyser
I'm not sure I understand this, but you need to report usage as soon as you can using the new billing meter
Have you had a chance to see this migration guide?
https://docs.stripe.com/billing/subscriptions/usage-based-legacy/migration-guide
crude hinge
Yes I did
I would prefer to send it hourly to not constrain my server too much. (Computing this value on each request is too much)
Is there any plan to add monthly pre-aggregation ? (In addition to hourly/daily)
cerulean geyser
Here are the available aggregation type:
https://docs.stripe.com/api/prices/object#price_object-recurring
there is no monthly or daily... this depends on the interval of the price used whether monthly, daily or other recurring period..
crude hinge
No, that's not the new meters
In the new meters it is event_time_window which can be day or hour
In the deprecated usage based you could set aggregation to last_during_period (which on a monthly plan would be monthly)
cerulean geyser
Ah yes sorry for the confusion...
cerulean geyser
In the new meters it is event_time_window which can be day or hour
Sorry but why not using hour as you are reporting usage hourly ?
crude hinge
I could but this is much more complicated already compared to the deprecated API : i would have to store the last MAU total count for the month, retrieve it hourly, compare it to the new mau count and sending the difference while also storing the new total count. It's completely doable but much more complicated than the deprecated api where i would just compute the total MAU count and send it
fossil schoonerBOT
digital beacon