Skip to content
github-actions[bot] edited this page Nov 18, 2026 · 2 revisions

How Lapilli judges alert rules, and how to run it: once over a period with lapilli verdict, or every hour with lapilli serve. The same pages are at lapilli.dev/docs and in the wiki, a copy of docs/ written again on each change; the README says what Lapilli is, and how to install it.

Start here

  • Getting started: install it, write down an incident or two, and read a first report on your own alerts; then keep judging with lapilli serve
  • Words: stones, firings, incidents, the ledger, and the rest of the words these pages use
  • Questions: what it needs, what it writes, and what it sends anywhere

Judging a period

  • How it judges: where firings and incidents come from, when a firing catches an incident, noisy rules and what to change, what a rule adds, when firings came, near misses, rules that changed
  • Use lapilli verdict: the commands, the reports it writes, the data sources it reads and how fast, and when it fails
  • The numbers: what each number is, and how to count it again from the report, without Lapilli
  • A cloud's own alarms: judging what CloudWatch, Azure Monitor, Google Cloud and OCI alarms fired
  • Rules on logs: Loki: LogQL rules replayed against Loki
  • Is the replay right?: --check-replay, the replay beside what really fired
  • What an alert says: --check-content, what each rule says when it fires, and how it is written

Before a change

Incidents

Reports

Every hour: lapilli serve

  • Keep judging: the ledger and its dashboard, teams, tasks and goals; checking it before it is deployed, the ledger in Postgres, several replicas, firings recorded elsewhere, tasks kept in step with a tracker
  • Notifications as they were sent: the notifications kept beside the firings
  • Changing rules: proposals, approval, and the change made where the rule is kept
  • Ask it from an agent: MCP at /mcp

Reference

  • Commands: every option of lapilli verdict, serve, preflight and ledger, as -h prints it
  • The HTTP API: every endpoint lapilli serve answers on, and the role each needs
  • Metrics: every metric lapilli serve exposes at /metrics
  • Upgrading: which version changed the ledger, and going back

And


This page is copied from docs/README.md, where it is changed: a pull request there changes it here.

Clone this wiki locally