Configure a Datadog SLO burn rate monitor to alert on accelerated error budget consumption

Steps

1. Create a Datadog SLO (metric-based or monitor-based) via the Datadog SLOs API or UI; record the SLO ID from the response as it is required to create the burn rate monitor.
2. Create an SLO alert monitor via POST /api/v1/monitor with type set to 'slo alert'; in the query field reference the SLO ID and set the alert_type to 'burn_rate' (as opposed to 'error_budget' for remaining budget alerts).
3. Set the burn_rate_threshold in the monitor options to the desired multiplier (e.g., 14.4 for a fast-burn alert consuming 2% of a 30-day budget in 1 hour); Datadog computes the actual error rate implied by this burn rate against the SLO target.
4. Configure the slo_alert_window (the short evaluation window, e.g., '1h') and the slo_burnrate_long_window (the long evaluation window, e.g., '5h') for the two-window burn rate check; the monitor fires only when both windows exceed the threshold.
5. Set thresholds.critical and optionally thresholds.warning to define severity levels; set notify_no_data carefully — for burn rate monitors, no data often means the service is healthy (no errors), so no-data alerting is typically disabled.
6. Add notify_end_states and renotify_interval to the monitor options for escalation behavior; configure the monitor's message with runbook links and error budget context using Datadog template variables like {{value}} (current burn rate) and {{threshold}}.