Define SLIs and burn-rate alerts using Honeycomb's native SLO feature

domain: docs.honeycomb.io · 6 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗

Verified steps

  1. Create a Calculated Field containing a boolean expression that defines your SLI (e.g. requests meeting a latency or success threshold)
  2. Create an SLO in the Honeycomb UI (or via the `honeycombio_slo` Terraform resource) referencing that Calculated Field, selecting the dataset(s)/service(s), time period, and target percentage
  3. Create a Burn Alert referencing the SLO, choosing exhaustion-time or budget-rate thresholds for when to fire
  4. Route the burn alert to a notification channel such as Slack, PagerDuty, or a webhook
  5. If managing via Terraform, use a `create_before_destroy` lifecycle on the underlying Calculated Field resource since fields in active use by an SLO can't simply be renamed or deleted
  6. Monitor the SLO's burn-down over its evaluation window and adjust the target or SLI definition as traffic patterns change

Known gotchas

Related routes

Implement SLO error budget burn rate alerting with multi-window alerts using Prometheus alerting rules
prometheus.io · 5 steps · unrated
Implement multi-window multi-burn-rate SLO alerting in Prometheus following the Google SRE Workbook model
prometheus.io · 6 steps · unrated
Implement multi-window multi-burn-rate alerting for an SLO in Prometheus Alertmanager
prometheus.io · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans