Skip to content

Production monitoring guide #813

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dahlia merged 9 commits into from
Jun 21, 2026
Merged

Production monitoring guide #813

Show file tree
Hide file tree
Changes from 4 commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
775b38a
Add production monitoring guide
dahlia Jun 21, 2026
0d8d584
Tag the monitoring guide's PromQL examples with a language
dahlia Jun 21, 2026
3c6cdad
Use increase() instead of rate() in count-based alerts
dahlia Jun 21, 2026
568f547
Qualify inbox latency for queued deployments
dahlia Jun 21, 2026
8a6bcd3
Note instance_id when aggregating queue depth
dahlia Jun 21, 2026
abc97d0
Distinguish permanent-status drops from abandoned deliveries
dahlia Jun 21, 2026
a5c8995
Make the gone-spike alert fire on a one-time burst
dahlia Jun 21, 2026
b194a90
Aggregate shared queue depth with max, not sum
dahlia Jun 21, 2026
c5964bf
Add the key-fetch histogram to the name-translation table
dahlia Jun 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .hongdown.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,10 +89,12 @@ proper_nouns = [
"ngrok",
"Object Integrity Proofs",
"OpenTelemetry",
"OpenTelemetry Collector",
"Piefed",
"Pixelfed",
"Pleroma",
"Podman Compose",
"Prometheus",
"RabbitMQ",
"Redis",
"scrypt",
Expand Down
1 change: 1 addition & 0 deletions docs/.vitepress/config.mts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -159,6 +159,7 @@ const MANUAL = {
{ text: "Linting", link: "/manual/lint.md" },
{ text: "Logging", link: "/manual/log.md" },
{ text: "OpenTelemetry", link: "/manual/opentelemetry.md" },
{ text: "Monitoring", link: "/manual/monitoring.md" },
{ text: "Benchmarking", link: "/manual/benchmarking.md" },
{ text: "Deployment", link: "/manual/deploy.md" },
],
Expand Down
7 changes: 7 additions & 0 deletions docs/manual/deploy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1343,6 +1343,13 @@ signals: CPU, RSS, event-loop lag, GC pauses, connection pool utilization
for your KV/MQ backend. None of these are Fedify-specific, but all of
them should be in place before you take real traffic.

Fedify exposes each of these federation signals as an [OpenTelemetry
metric](./opentelemetry.md#instrumented-metrics). The [*Production
monitoring* guide](./monitoring.md) turns them into a starter dashboard and
a set of alert rules, with PromQL examples, guidance on which failures should
page versus prompt investigation, and notes on keeping metric cardinality
bounded.


ActivityPub-specific operational concerns
-----------------------------------------
Expand Down
Loading