Nobl9 alerts
When an incident is triggered, you can send an alert to a notification engine or tool. Nobl9 also supports integration with a web endpoint by using webhooks where you define the endpoint and parameters to pass.
Alerts in Nobl9 can be sent to several different tools, including PagerDuty, MS Teams, Slack, Discord, Jira, Opsgenie, and ServiceNow. Nobl9 also supports email alerts, and you can use webhooks to send alerts to any service that has a REST API, such as FireHydrant, Asana, xMatters, and many more.
With configured alerting, you can react immediately to incidents that matter from the perspective of the user experience of your service. Alerts improve the control of what’s going on in your system and empower you to do better-contributing factor analysis when something goes wrong.
Here are important things to keep in mind while setting up your alerts:
-
Both our attention and energy are limited resources. SLO alerts must correspond to real and urgent issues of your system.
-
Keep in mind that to improve your monitoring, these alerts have to be well-defined and need to evolve together with your system.
With Nobl9 system annotations feature, you can see an annotation added to the SLO objective charts by default each time an alert is triggered or resolved (they are displayed regardless of whether an alert policy is silenced). For more detailed information, refer to the SLO annotations documentation.
