#ferre_best-practices

1 messages ¡ Page 1 of 1 (latest)

slender needleBOT
#

👋 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/1296785960058748979

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

versed haven
#

AFAIK, there is no end of support. It's just belongs to the legacy part.

#

Out of curiosity, is there any limitation on your use case blocking you from migrating to the new integration ?

ornate egret
#

I had a ticket yesterday:

I want to bill my users based on 3 things
1: 10 euros per property per month
2: 3 euros per unit per month
3: 2 euros per user per month

Usage can fluctuate month per month, and users should be billed based on peak usage in the current billing period. We dont know how much they are going to use every month so we can decide quantities beforehand. If they create 4 properties and delete 1 in billing period (aug-sep) then they should be billed for 4, but if they then dont do anything for (sept-oct) they should be billed for 3 because that is their peak usage during those billing periods.

and i think that the max aggregation is really helpful here, and the meters do not support that (yet?). So i want to try and set it up with the legacy system, but i dont want to do that if it gets removed soon

versed haven
#

and the meters do not support that (yet?)
What is the exact limitation you were facing ? have you tried to make some tests ?

#

If they create 4 properties and delete 1 in billing period (aug-sep) then they should be billed for 4, but if they then dont do anything for (sept-oct) they should be billed for 3 because that is their peak usage during those billing periods.
This can be handled in your integration and report usage accordingly.

slender needleBOT
versed haven
ornate egret
#

yes i have a test environment, where i tried it with count meters and sum meters, Maybe my integration is wrong, let me lay it out real quick:

I store current and peak usage for my customers (for each of the items, properties, units, users)

i have a backgroundservice that runs everyday at 3am that should report usage. The problem i am facing is that currently i dont check the current meter value, i would just always like to pass in the value that is supposed to be billed to the customer (peak usage), but with both count and sum meters, this does not work.

I think i would need to check the existing value and then report usage based on the difference on my server (e.g. stripe meter says 5, my server peak usage says 8, so i report 3 to a sum meter), is that how it is supposed to work?

raven helm
#

Yes you can't increment the usage with a Meter like you could/can with the legacy API

#

So what you describe is somethign you'd need to handle yes

ornate egret
#

okay, so i just want to make sure i understand:

i should: check current meter values and compare them to my own stored value, and then report the difference?

raven helm
#

Yes, or refactor your internal usage tracking accordingly so that it just persists a 'daily' sum you can send

ornate egret
#

alright, ill give it a shot, and if i cant get it to work ill have to switch over to the legacy api

#

thanks