Error budgets for your services
An objective says how much failure a service may have over 28 days, for example 99.9% of requests succeed. Varqeni reads how much it is spending from the same numbers it already watches.
AvailabilityAvailable to everyone with early access to Varqeni.
Steps
- Your administrator adds an objective to a service: availability (the share of requests that succeed) and, if you like, latency (the share answered in under a time you choose).
- In Service, Error budgets shows each objective, how much of its budget is left and how fast it is being spent.
- Burning fast: over the last hour and the last five minutes it spent its budget more than 14 times too fast, enough to use it all within about two days. That pages, unless another check already names a cause for the service.
- Burning slowly: over six hours and thirty minutes it spent more than 6 times too fast. That is shown, never paged.
What you should see: In the lab it named a fast burn and showed a slow burn, without false alarms, in 30 of 30 blind trials, with the lab's shortened windows.
What it can and cannot do
Can
- Show each objective's budget left, page on a fast burn and show a slow one, from the numbers Service Operations already reads.
Cannot
- Page on a slow burn, or set objectives from the console yet. Your administrator sets them.
Related articles
- Read your services under ServiceUnder Service, the console shows each service you use, whether it answers and how fast, how many of its requests fail, which services it calls, your scheduled jobs, and what was deployed in the last 30 minutes.
- What each cause meansThe causes Varqeni names for a change data capture pipeline, in plain words.
- The Reports viewHow fast pages are answered and incidents end, what makes the most incidents and who carries the pager, across every system.
Still stuck? Contact support or email info@fortisdatagroup.com.