No data anomaly alerts

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

Nobl9 users can stay on top of their SLOs by configuring no data notifications to detect and alert on missing data anomalies. These notifications ensure that gaps in monitoring data or reporting do not go unnoticed, thereby enhancing the reliability of your systems.

With this SLO monitoring feature, you can customize anomaly detection settings for your SLOs to define how and when to receive notifications if your SLO fails to report data.

Anomaly alerts are sent using an available alert method. A notification includes the information about the anomaly and a link to the affected SLO details.

By default, alerts are triggered when the SLO reports no data during 15 minutes. However, you can set a custom time frame, from 5 minutes to 31 days.

Scope of support

No data anomaly alerting supports the following alert methods:

• Email

• MS Teams

• Opsgenie

• Slack

• Webhook

  

  Slack notification for the "No data" anomaly.

Setting up anomaly alerts

Before configuring anomaly alerts for your SLO, make sure you have the following:

• At least one of the supported alert methods is configured
• You have access to it

You can set up anomaly alerting in the Nobl9 Web application, applying a YAML definition with sloctl apply, or using the Nobl9 Terraform provider.

Nobl9 Web application

To set up anomaly alerting in the Nobl9 Web application, select No data anomaly alert in Step 5 of the SLO wizard. Then, specify how long your SLO must wait for data before sending the notification and select your preferred alert method:

Setting up no data notification on the Nobl9 Web

sloctl

To set up anomaly alert using sloctl, configure the noData parameters in your SLO YAML definition:

Example of anomalyConfig in an SLO YAML definition

- apiVersion: n9/v1alpha
  kind: SLO
  metadata:
    name: my-slo
    project: my-project
  spec:
    alertPolicies: []
    anomalyConfig:
      noData:
        alertMethods:
          - name: my-alert-method-1
            project: my-project-1
          - name: my-alert-method-1
            project: my-project-2
        alertAfter: 1h

Then, apply it with sloctl apply.

Nobl9 Terraform provider

To set up anomaly alert using Nobl9 Terraform provider, follow the below pattern:

Example of anomaly notifications configuration to use with the Nobl9 Terraform provider

[...]
  anomaly_config {
     no_data {
       alertAfter = "15m"
  
       alert_method {
         name = "my-alert-method-1"
         project = "my-project-1"
       }
        
       alert_method {
         name = "my-alert-method-2"
         project = "my-project-2"
       }
     }
   }

No data anomalies in a nutshell

• No data anomaly alerts and kind: Alert are not the same.
  While kind: Alert is an individual entity in Nobl9 that you can retrieve using sloctl get alerts, no data anomaly alerting is part of the SLO configuration and cannot exist without an SLO.
• No data anomaly alerts are set per SLO objectives.
  An individual notification is sent for every SLO objective when it fails to report data for your specified time frame.
• You can add up to five alert methods for anomaly alerting per SLO.
• To get notified on no data anomalies, you must have access to the SLO and alert method used to send notifications.

Useful links

For a more in-depth look, consult additional resources:

Query delayNobl9 featuresNo data troubleshootingTroubleshootingSLOs general troubleshootingTroubleshootingData source troubleshootingTroubleshootingNetwork connectivity requirementsData sources: requirementsPermissions and accessRequirements