Service Mapped
oncall.service-mapped
Verifies the component is mapped to an on-call service. Fails when a collector looked for one and found none (.oncall.service_lookup), naming the places it looked; skips when no collector looked, or a lookup couldn't finish.
Compatible Integrations
This guardrail works with the following integrations. Click to see how to use Service Mapped 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/oncall@v1.0.5
include: [service-mapped]
# with: ...How This Guardrail Works
This guardrail is part of the On-Call 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 →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 |
|---|---|---|---|
min_participants
|
Optional |
2
|
Minimum number of on-call rotation participants required |
On-Call Guardrails
This guardrail is part of the On-Call Guardrails policy, which includes 4 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 300+ built-in guardrails.
AI agent rules & prompt files
Post-mortem action items
Security & compliance policies
Testing & quality requirements