Slo Defined
observability.slo-defined
Verifies that at least one Service Level Objective is defined for the service by checking .observability.slo.defined is true. Fails if observability data is present but no SLOs are configured. Skips cleanly when no observability source has written data for this component. SLO data is provided by collectors that support SLOs (e.g. Datadog). Grafana-only deployments will skip this check unless SLO data is populated from another source.
Compatible Integrations
This guardrail works with the following integrations. Click to see how to use Slo Defined with each collector.
Enable This Guardrail
Add the parent policy to your lunar-config.yml to enable this guardrail.
policies:
- uses: github://earthly/lunar-lib/policies/observability@v1.0.5
include: [slo-defined]
# with: ...How This Guardrail Works
This guardrail is part of the Observability 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 →
Observability Guardrails
This guardrail is part of the Observability Guardrails policy, which includes 3 guardrails for operational readiness.
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.
AI agent rules & prompt files
Post-mortem action items
Security & compliance policies
Testing & quality requirements