Skip to content

docs: the metric families are populated now #11

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
oreofeolurin merged 1 commit into from
Aug 30, 2026
Merged

docs: the metric families are populated now #11

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
13 changes: 8 additions & 5 deletions docs/deployment/clustering.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -200,11 +200,14 @@ Divergence detection is implemented; automatic repair is not — see
:::

:::note
**Some families are registered but not yet incremented.** Nothing records the
per-shard or per-stream counters on the write paths, so `flo_shard_*` and the
per-stream totals currently export as `0`. Cluster-level names such as
`flo_cluster_nodes`, `flo_raft_leader_elections_total` and `flo_gossip_members`
are not implemented at all.
**Cluster-level names such as `flo_cluster_nodes`,
`flo_raft_leader_elections_total` and `flo_gossip_members` are not
implemented** — do not build scrape configs or alerts on them. The families
documented above are populated from the live write paths.

One exception worth knowing: `flo_tiered_log_cold_hits_total` is always `0`.
The read path consults the hot ring and the warm store only, so a cold-tier
read is never counted there rather than the counter being unwired.
:::

## Recommended Topologies
Expand Down
Loading