Usage alerts let you set a spending limit and choose threshold percentages of that limit. When usage in the current billing period crosses a threshold, Sevalla sends an email to the recipients you configure. You can set alerts at two levels:Documentation Index
Fetch the complete documentation index at: https://docs.sevalla.com/llms.txt
Use this file to discover all available pages before exploring further.
- Company - tracks total spending across every project, application, database, static site, object storage, and load balancer in your company.
- Project - tracks spending for the services that belong to a single project.
How alerts work
Each alert configuration has:- A spending limit in USD.
- One or more threshold percentages (between 1 and 100, up to 10 per configuration). For example, 50%, 75%, and 90%.
- One or more email recipients.
Create a company-wide alert
Open the Usage page and click Add alert. Set the following:- Spending limit - the USD amount the thresholds are calculated from.
- Thresholds - one or more percentages of the limit. Add up to 10 thresholds.
- Recipients - one or more email addresses to notify.
Create a project alert
Open the project, go to its Usage tab, and click Add alert. The fields are the same as for a company alert, but the thresholds are calculated only against the spending of services that belong to that project. A project alert is independent of the company alert. If you have both, you can be notified for the project crossing its limit, the company crossing its limit, or both.Update or delete an alert
From the same Usage page, you can:- Change the spending limit, thresholds, or recipients.
- Delete the alert. Once deleted, no further emails are sent for it.
Notes
- Usage alerts are notifications only. They do not pause, suspend, or limit any of your services when a threshold is reached.
- Thresholds are evaluated against gross usage (including tax) for the current billing period, matching the totals shown on the Usage page.
- If you change the spending limit or thresholds mid-period, the new values take effect on the next hourly check. Thresholds that already fired this period stay fired until the next period starts.