[adriangb]

Summary

The Service Levels guide says that Logfire omits a burn-rate tier when the reliability target is too low for that tier to fire. Logfire now behaves differently:

• Every reliability target always has all three burn-rate alerts (fast, medium and slow burn).
• A tier that cannot fire at the current target is kept but not evaluated. The target detail page shows it as Disabled with Target too low to fire, and its alert page says that the reliability target is too low for the alert to fire.
• A disabled tier does not count as an active alert.
• If the target is raised so that the tier can fire, the same alert runs again with its notification channels.

This PR updates docs/guides/web-ui/service-levels.md to describe that behavior. It gives the target thresholds at which the fast burn (about 93.06%) and medium burn (about 83.34%) tiers can fire. It also says that the channels you choose when you create a target are a starting set for its three alerts, and that you can change the channels of each alert later, which matches the setup wizard.

When to merge

This documents behavior in the next Logfire release. Merge it when that release is out.

Preview

I built the page locally with the unified docs preview (make docs-serve flow), together with #2459. The page renders, and every link on it resolves: the internal links to Pydantic Evals, Infrastructure as Code, Alerts, SQL Workbench, Live view and LLMs, the in-page anchors, and the Google SRE Workbook link. Please still check the hosted preview.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Team

Run ID: 59d6ee4a-640d-4d6a-863a-dd2667a49800

📥 Commits

Reviewing files that changed from the base of the PR and between 6debccc and ecef9a4.

📒 Files selected for processing (1)

• docs/guides/web-ui/service-levels.md

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• pydantic/logfire (manual)
• pydantic/pydantic-ai (manual)

Included review availability: Your plan provides up to 8 included reviews per hour; 1 remains after this review.

---

📝 Walkthrough

Walkthrough

The guide now states that reliability targets can use any percentage below 100%, with presets from 99% to 99.99% and a 99.9% default. Each target generates all three burn-rate alerts and supports initial notification-channel selection. Tiers that cannot fire remain disabled, do not count as active alerts, and resume when the target is raised. The guide also gives minimum targets for fast- and medium-burn tiers.

Priority: ⬇️ Low

Merge Risk: ⚪ Minimal · up to ecef9

The documentation changes are consistent with the supplied objectives and ready to merge.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main documentation change: it documents disabled burn-rate tiers for low reliability targets.
Description check	✅ Passed	The description is directly related to the documentation changes and explains the updated burn-rate alert behavior, thresholds, and notification channels.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

✨ Simplify code

• Commit to this branch
• Create a new PR

---

_{Comment @coderabbitai help to get the list of available commands.}

[cubic-dev-ai]

All reported issues were addressed across 1 file

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>