Skip to content

Grafana Alerts labeling Guide

Imported from Confluence

Content may be outdated. Verify before following any procedures. View original | Last updated: September 2025

This document explains how to correctly label alerts in Grafana so they are routed to the right destination (Slack, PagerDuty, Opsgenie).
Following these rules ensures alerts go to the correct team with the right priority.

Every alert must have exactly 2 labels:

1️⃣ Category Label (choose one)

This defines what type of issue the alert represents.

devops_alerts = "true"        # Infrastructure / platform related issues
application_alerts = "true"   # Business logic or application related issues
  • Use devops_alerts if the alert is about infrastructure, networking, or system health.
  • Use application_alerts if the alert is about backend, business processes, or customer-facing features.

2️⃣ Severity Label (choose one)

This defines how urgent the issue is.

info = "true"      # Informational → goes to muted/default channels
warning = "true"   # Minor issues → Slack channels
major = "true"     # Significant impact → PagerDuty / Opsgenie
critical = "true"  # System down → PagerDuty / Opsgenie
  • info: Alerts for visibility only (no action needed).
  • warning: Alerts that might require action, but not urgent.
  • major: Alerts with real customer/business impact → require on-call response.
  • critical: Alerts for severe outages//business impact**** → immediate escalation.

📡 Routing Rules

Based on the combination of category + severity, alerts are routed as follows:

🔹 DevOps Alerts (devops_alerts: "true")

  • warning = true → Slack channel: #bln-escalation
  • major = true or critical = true → PagerDuty: pagerduty-devops

🔹 Application Alerts (application_alerts: "true")

  • warning = true → Slack channel: #fbb_day_alerts or it can be #bln-escalation from devops if application team don't have dedicated slack channel
  • major = true or critical = true → Opsgenie: FairbidBackend - opsgenie api or pagerduty

🔹 Info Alerts (any category)

  • info = true → Slack channel: #bln-escalation-muted
  • If no category is specified, they will still go to the muted/default channel.

Here is the example  Grafana - Routes