Alert presets
Alert presets are a way to set up alert policies quickly using predefined templates. They are designed to help you get started with alerting in a matter of minutes, using Nobl9 recommended sets of policies in Nobl9.
Overviewβ
The following presets are available in Nobl9:
Configuring alert presetsβ
To see available alert presets, go to the Alerts view and click the button. This view shows a list of alert presets, each with a name, description, and a set of default values for alert policy configuration.
![Creating alert policy from preset](/img/alerting/presets/presets-form.png)
You can choose one preset and apply it by clicking the Use Preset button.
Customizing the presetβ
You may need to customize the alert preset to suit your needs better. There are two ways to create a custom alert policy in Nobl9:
- You can select the custom preset in step 1 of the wizard.
- Or, you can modify an existing alert preset by replacing its default values with your own. Once you're done editing, you can apply the preset to create an alert policy with your custom values. Your edited preset will then be accessible from the alert policies view.
Nobl9 won't persist the customized version of an alert preset. Opening the alert preset view again will restore the original preset definitions.
If you want to re-use the same custom configuration of a preset for a different alert policy, you can duplicate the alert policy created using the customized Alert Preset. The easiest way to do that is to copy the YAML configuration of your customized preset by running thesloctl get alertpolicies [alert_policy_name]
command and copying the specs.[...]
block.
Starting from scratchβ
If you don't want to use any preset, you can start an alert policy from scratch by selecting a Custom option on the Presets list.
![Creating alert policy from preset](/img/alerting/presets/presets-custom.png)
Alert policy presets in YAMLβ
Presets are also available in the YAML format.
To use them, just copy-paste the configuration, change the project
and add a preferred alertMethod
.
- Fast burn
- Slow burn (long windows)
- Slow burn (short windows)
- Budget almost exhausted
- Fast exhaustion above budget
- Fast exhaustion below budget
- Slow exhaustion for long window SLOs
- Slow exhaustion for short window SLOs
- Fast budget drop
- Slow budget drop
apiVersion: n9/v1alpha
kind: AlertPolicy
metadata:
name: fast-burn
displayName: Fast burn (20x5min)
project: default
spec:
alertMethods: []
conditions:
- alertingWindow: 5m
measurement: averageBurnRate
value: 20
op: gte
coolDown: 5m
description: Thereβs been a significant spike in burn rate over a brief period.
severity: High
apiVersion: n9/v1alpha
kind: AlertPolicy
metadata:
name: slow-burn
displayName: Slow burn (1x2d and 2x15min)
project: default
spec:
alertMethods: []
conditions:
- alertingWindow: 48h
measurement: averageBurnRate
value: 1
op: gte
- alertingWindow: 15m
measurement: averageBurnRate
value: 2
op: gte
coolDown: 5m
description: The budget is slowly being exhausted and not recovering.
severity: Medium
apiVersion: n9/v1alpha
kind: AlertPolicy
metadata:
name: slow-burn
displayName: Slow burn (1x12h and 2x15min)
project: default
spec:
alertMethods: []
conditions:
- alertingWindow: 12h
measurement: averageBurnRate
value: 1
op: gte
- alertingWindow: 15m
measurement: averageBurnRate
value: 2
op: gte
coolDown: 5m
description: The budget is slowly being exhausted and not recovering.
severity: Medium
apiVersion: n9/v1alpha
kind: AlertPolicy
metadata:
name: budget-almost-exhausted-20
displayName: Budget almost exhausted (20%)
project: default
spec:
alertMethods: []
conditions:
- measurement: burnedBudget
value: 0.8
op: gte
coolDown: 5m
description: The error budget is nearly exhausted (20%)
severity: Medium
apiVersion: n9/v1alpha
kind: AlertPolicy
metadata:
displayName: Fast exhaustion above budget
name: fast-exhaustion-above-budget
project: default
spec:
alertMethods: []
conditions:
- alertingWindow: 10m
measurement: timeToBurnBudget
op: lt
value: 72h
- lastsFor: 0m
measurement: burnedBudget
op: lt
value: 1
coolDown: 5m
description: The error budget is exhausting significantly and there's still some
budget remaining.
severity: High
apiVersion: n9/v1alpha
kind: AlertPolicy
metadata:
displayName: Fast exhaustion below budget
name: fast-exhaustion-below-budget
project: default
spec:
alertMethods: []
conditions:
- alertingWindow: 10m
measurement: timeToBurnEntireBudget
op: lte
value: 72h
- lastsFor: 0m
measurement: burnedBudget
op: gte
value: 1
coolDown: 5m
description: The error budget is exhausting significantly and there's no remaining
budget left.
severity: High
apiVersion: n9/v1alpha
kind: AlertPolicy
metadata:
displayName: Slow exhaustion for long window SLOs
name: slow-exhaustion-long-window
project: default
spec:
alertMethods: []
conditions:
- alertingWindow: 48h
measurement: timeToBurnBudget
op: lt
value: 480h
- alertingWindow: 15m
measurement: timeToBurnBudget
op: lt
value: 480h
- lastsFor: 0m
measurement: burnedBudget
op: lt
value: 1
coolDown: 5m
description: The error budget is exhausting slowly and not recovering.
severity: Low
apiVersion: n9/v1alpha
kind: AlertPolicy
metadata:
displayName: Slow exhaustion for short window SLOs
name: slow-exhaustion-short-window
project: default
spec:
alertMethods: []
conditions:
- alertingWindow: 12h
measurement: timeToBurnBudget
op: lt
value: 120h
- alertingWindow: 15m
measurement: timeToBurnBudget
op: lt
value: 120h
- lastsFor: 0m
measurement: burnedBudget
op: lt
value: 1
coolDown: 5m
description: The error budget is exhausting slowly and not recovering.
severity: Low
apiVersion: n9/v1alpha
kind: AlertPolicy
metadata:
name: fast-budget-drop
displayName: Fast budget drop (10% over 15 min)
spec:
description: The budget dropped by 10% over the last 15 minutes and is not recovering.
severity: High
coolDown: "5m"
conditions:
- measurement: budgetDrop
value: 0.1
alertingWindow: 15m
op: gte
apiVersion: n9/v1alpha
kind: AlertPolicy
metadata:
name: slow-budget-drop
displayName: Slow budget drop (5% over 1h)
spec:
description: The budget dropped by 5% over the last 1 hour and is not recovering.
severity: Low
coolDown: "5m"
conditions:
- measurement: budgetDrop
value: 0.05
alertingWindow: 1h
op: gte
Keep in mind that alert policies are limited to a specific project. This means they must be assigned to the same project as the SLO they are associated with. The preset options mentioned above create policies in the default
project.
Before applying them, double-check that you've selected the correct project.
Alert presets in Terraformβ
Alert presets are also available in Terraform. They can be treated as an example, to set up your own alert policies using predefined, Nobl9 recommended configuration.
You can access them in our Terraform Documentation.