Skip to main content
    DevOps
    Way of Working
    1. Home
    2. Tools
    3. Alert Threshold

    Alert Threshold Calculator

    Calculate SLO-based alert thresholds using multi-window, multi-burn-rate alerting

    SLO Configuration

    Select a preset or configure custom SLO targets

    High-availability API with 99.9% uptime SLO

    Use Case: Customer-facing API, ~43 minutes downtime/month allowed

    SLO Target

    99.90%

    Error Budget

    0.100%

    Allowed Downtime

    43 minutes

    per 30d

    Calculated Alert Thresholds

    Multi-window, multi-burn-rate alerts based on Google SRE best practices

    Critical: 14.4x Error Budget Burn

    14.4x faster than acceptable error rate

    CRITICAL

    Detection Window

    1h

    Lookback Window

    1h

    Budget Consumed

    2.0%

    Time to Exhaustion

    2 days

    Critical: 6x Error Budget Burn

    6x faster than acceptable error rate

    CRITICAL

    Detection Window

    6h

    Lookback Window

    6h

    Budget Consumed

    5.0%

    Time to Exhaustion

    5 days

    Warning: 3x Error Budget Burn

    3x faster than acceptable error rate

    WARNING

    Detection Window

    24h

    Lookback Window

    24h

    Budget Consumed

    10.0%

    Time to Exhaustion

    1 weeks

    Warning: 1x Error Budget Burn

    1x faster than acceptable error rate

    WARNING

    Detection Window

    7d

    Lookback Window

    7d

    Budget Consumed

    23.3%

    Time to Exhaustion

    4 weeks

    Export Alert Configuration

    Copy-paste Prometheus/Grafana alert rules

    # API Availability - 99.90% SLO
    # Error Budget: 0.10% over 30d
    
    groups:
      - name: api_availability_alerts
        interval: 30s
        rules:
    - alert: "Critical: 14.4x Error Budget Burn"
      expr: |
        (
          sum(rate(http_requests_total{status=~"5.."}[1h]))
          /
          sum(rate(http_requests_total[1h]))
        ) > 0.0144
      for: 1h
      labels:
        severity: critical
        slo: API Availability
      annotations:
        summary: "High error rate detected (14.4x burn rate)"
        description: "Error budget will be exhausted in 2 days"
    
    - alert: "Critical: 6x Error Budget Burn"
      expr: |
        (
          sum(rate(http_requests_total{status=~"5.."}[6h]))
          /
          sum(rate(http_requests_total[6h]))
        ) > 0.006
      for: 6h
      labels:
        severity: critical
        slo: API Availability
      annotations:
        summary: "High error rate detected (6x burn rate)"
        description: "Error budget will be exhausted in 5 days"
    
    - alert: "Warning: 3x Error Budget Burn"
      expr: |
        (
          sum(rate(http_requests_total{status=~"5.."}[24h]))
          /
          sum(rate(http_requests_total[24h]))
        ) > 0.003
      for: 24h
      labels:
        severity: warning
        slo: API Availability
      annotations:
        summary: "High error rate detected (3x burn rate)"
        description: "Error budget will be exhausted in 1 weeks"
    
    - alert: "Warning: 1x Error Budget Burn"
      expr: |
        (
          sum(rate(http_requests_total{status=~"5.."}[7d]))
          /
          sum(rate(http_requests_total[7d]))
        ) > 0.001
      for: 7d
      labels:
        severity: warning
        slo: API Availability
      annotations:
        summary: "High error rate detected (1x burn rate)"
        description: "Error budget will be exhausted in 4 weeks"
    DevOps
    Way of Working

    DevOps practices for the entire delivery lifecycle

    © 2019-2026 devopswow.com. Created by Burhan Öcüt

    PartnersAboutPrivacyTermsCookies