Notifications

Notification Details

• Summary: A brief, readable summary of the issue, like "High CPU usage detected on server-1Copy."
• Description: Detailed information about the issue, such as "CPU usage has exceeded 90% for more than 5 minutes on instance server-1Copy."

Configure Notification Channels

When setting up checks, you can configure notification channels to receive alerts if a check fails. If you already have existing notification channels, simply select one from the list. Alternatively, you can create a new notification channel tailored to your needs.
Choose from the currently supported notification integrations below to configure how you receive alerts:

• Alertmanager
• BetterStack
• Email
• Incident.io
• Jira Service Management
• Microsoft Teams
• Opsgenie
• PagerDuty
• Slack Bot
• Slack Webhook
• Webhook
  

Labels & Annotations

Labels

• Purpose: Labels are key-value pairs that categorize and provide metadata for the alert. They define important aspects like the source of the alert, its severity, and contextual information that can help in filtering, routing, and silencing alerts when using Alertmanager.
• Examples: Common labels might include:
  • severityCopy: Defines the urgency level of the alert, such as critical, warning, or info.
  • alertnameCopy: A unique name for the alert rule, like HighCPUUsage or MemoryLeak.
  • instanceCopy: Identifies the instance where the alert originated, like server-1 or node-xyz.
  • serviceCopy: Indicates the job or service name associated with the alert, like web-service or database-service.

Annotations

• Purpose: Annotations provide descriptive, human-readable information about the alert. They contain details that aid in understanding and troubleshooting the alert, often presented to the user in notification messages.
• Examples: Common annotations might include:
  • messageCopy: Detailed information about the issue, such as "CPU usage has exceeded 90% for more than 5 minutes on instance server-1."
  • runbook_urlCopy: A link to documentation or a playbook on how to respond to the alert.
• Note: Summary and Description that can be configured - are effectively annotations.