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
We should add a spending limit to Lagon Cloud, that prevents unexpected and unwanted bills.
This limit can be added per function and/or per organization and corresponds to a certain number of requests made during the month. When approaching the limit, the user should get warnings on the dashboard and by email.
Example
Let's assume I don't want to pay more than 5€ for requests served per month because my traffic is relatively low. This corresponds to 5,000,000 requests, so I'll add this limit on the Dashboard.
One day, my project suddenly get a lot of traffic. A warning is triggered when reaching 75% of my limit (3,750,000 requests for me), and another one at 90% (4,500,000 requests for me).
I can choose to raise or disable the limit to make sure every user is able to access my project, or I can keep the limit to avoid spending too much (but that means when reaching the 5,000,000th request, the Function will be disabled).
The text was updated successfully, but these errors were encountered:
We should add a spending limit to Lagon Cloud, that prevents unexpected and unwanted bills.
This limit can be added per function and/or per organization and corresponds to a certain number of requests made during the month. When approaching the limit, the user should get warnings on the dashboard and by email.
Example
Let's assume I don't want to pay more than 5€ for requests served per month because my traffic is relatively low. This corresponds to 5,000,000 requests, so I'll add this limit on the Dashboard.
One day, my project suddenly get a lot of traffic. A warning is triggered when reaching 75% of my limit (3,750,000 requests for me), and another one at 90% (4,500,000 requests for me).
I can choose to raise or disable the limit to make sure every user is able to access my project, or I can keep the limit to avoid spending too much (but that means when reaching the 5,000,000th request, the Function will be disabled).
The text was updated successfully, but these errors were encountered: