Create an alert policy

Reading time: 0 minute(s) (0 words)

See how to create an alert policy.

Tired of reading? Check out the video tutorial!

With a created alert method, you can configure an alert policy that expresses a set of conditions you want to track or monitor. The conditions for an alert policy define what is monitored and when to activate an alert: when the performance of your service is declining, Nobl9 will send a notification to a predefined channel.

Configuration

Follow these steps to create an alert policy in the Nobl9 UI:

1. Go to the Alerts tab.
2. Click .
3. Step 1

Select preset

Alert presets are a way to set up alert policies quickly using predefined templates.


The following presets are available:

• Fast burn
• Slow burn for long window SLOs
• Slow burn for short window SLOs
• Budget almost exhausted



Image 1: Creating new Alert Policy from a Preset



4. Step 2

Define your alert conditions

Alert conditions are rules that determine when Nobl9 will trigger an alert. Each rule corresponds to a specific condition type, defined as a function of time, burn rate, or remaining error budget. You can create up to three conditions for each alert policy.





• The Remaining error budget would be exhausted in the near or distant future. In this condition, exhaustion time prediction becomes more sensitive as your remaining budget decreases. Once your SLO has no error budget left, even the slightest amount of burn will trigger an alert.
• The Remaining error budget is the amount left from the error budget set in the SLO.
• The Entire error budget would be exhausted in the near or distant future. This prediction is based on the allocation of your entire error budget and depends only on the current burn rate. Use it to define alerts based on time rather than the burn rate function and avoid the remaining budget value impacting the prediction.
• The Average error budget burn rate is greater or equal to the threshold and lasts for some period. This alert condition helps catch burn rate spikes independently of the burned budget.
• The remaining error budget is below the threshold. It allows for the most straightforward configurations that will alert you when you reach a specific level of error budget, regardless of how quickly or slowly you reach it.






Image 2: Step 2 of alert policy wizard

5. Step 3

Add alert method and labels

• Select the previously created alert method that you'd like to use and select the relevant integration from the list menu.
• Select or add Labels.
  Labels have a specific format and must conform to the following rules:
  

  • key: value format
  • key can contain only lowercase alphanumeric characters, underscores, and dashes; must start with a letter and end with an alphanumeric character; maximum length 63 characters
  • value can contain Unicode characters; maximum length 200 characters
  • Maximum of 20 labels attached



Image 2: Step 3 of alert policy wizard



6. Click Create Alert Policy.

For more information on alert policy & alert method lifecycle, refer to the Alert methods.

Good job! You'll now receive a notification to a predefined channel in case something goes wrong.