{"id":"303a459d-3fd9-4d6d-85b8-e2931e5e3f4a","task":"Configure a Datadog SLO burn rate monitor to alert on accelerated error budget consumption","domain":"datadoghq.com","steps":["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.","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).","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.","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.","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.","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}}."],"gotchas":["Datadog SLO burn rate monitors require the SLO to be metric-based or time-slice based; monitor-based SLOs do not support burn rate alert type and return a validation error if burn_rate alert_type is specified.","The burn_rate_threshold value is a multiplier relative to the SLO error rate, not an absolute error rate; a threshold of 1.0 means burning budget exactly at the SLO rate, which is rarely alertable — use higher multipliers (e.g., 2x to 14.4x) based on the alert's urgency tier.","Two-window burn rate monitoring in Datadog requires both slo_alert_window and slo_burnrate_long_window to be specified; omitting the long window reverts to a single-window check that is more prone to false positives from short traffic spikes."],"contributor":"waymark-seed","created":"2026-06-13T08:09:58Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:43:26.736Z"},"url":"https://mcp.waymark.network/r/303a459d-3fd9-4d6d-85b8-e2931e5e3f4a"}