Slo Burn Rate Alert

✓ Guardrail Datadog Guardrails Experimental Operational Readiness

datadog.slo-burn-rate-alert

Verifies that every declared SLO has a matching burn-rate alert monitor. Datadog offers a dedicated "SLO alert" monitor type that references an SLO by ID and fires when the error-budget burn rate exceeds a threshold, preventing fire-and-forget SLOs that silently drift. Cross-references .observability.native.datadog.api.slos against .observability.native.datadog.api.monitors and fails if any SLO lacks a monitor of type slo alert bound to its ID. Skips cleanly when no SLOs are defined or when the Datadog collector hasn't written native data.

datadog slo error budget burn rate monitors

Get Started View All Datadog Guardrails

Compatible Integrations

This guardrail works with the following integrations. Click to see how to use Slo Burn Rate Alert with each collector.

Slo Burn Rate Alert + Datadog Collector Provides Datadog monitor and SLO data at .observability.native.datadog.api

→

Enable This Guardrail

Add the parent policy to your lunar-config.yml to enable this guardrail.

📄 lunar-config.yml

policies:
  - uses: github://earthly/lunar-lib/policies/datadog@v1.0.5
    include: [slo-burn-rate-alert]
    # with: ...

How This Guardrail Works

This guardrail is part of the Datadog Guardrails policy. It evaluates data collected by integrations and produces a pass/fail check with actionable feedback.

When enabled, this check runs automatically on every PR and in AI coding workflows, providing real-time enforcement of your engineering standards.

Learn How Lunar Works →

↓ Integrations Gather Data

Collectors extract metadata from code, CI pipelines, tool outputs, and scans

{ } Centralized as JSON

All data merged into each component's unified metadata document

✓ This Guardrail Checks Current

Slo Burn Rate Alert runs and provides pass/fail feedback

Configuration Options

These inputs can be configured in your lunar-config.yml to customize how the parent policy (and this guardrail) behaves.

Input	Required	Default	Description
`pager_handle_prefixes`	Optional	`pagerduty,opsgenie,victorops`	Comma-separated list of Datadog notification handle prefixes that count as a pager target. Any monitor message containing at least one `@<prefix>-*` handle from this list passes the `monitor-has-pager-target` check. Defaults cover PagerDuty, Opsgenie, and VictorOps.

Datadog Guardrails

This guardrail is part of the Datadog Guardrails policy, which includes 2 guardrails for operational readiness.

View Policy

Ready to Automate Your Standards?

See how Lunar can turn your AGENTS.md, engineering wiki, compliance docs, or postmortem action items into automated guardrails with our 200+ built-in guardrails.

Works with any process

AI agent rules & prompt files

Post-mortem action items

Security & compliance policies

Testing & quality requirements

Automate Now

Paste your AGENTS.md or manual process doc and get guardrails in minutes

Book a Demo