Skip to content

Update the metric in the cluster endpoint description #2516

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

Update the metric in the cluster endpoint description #2516

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
2 changes: 1 addition & 1 deletion modules/ROOT/pages/clustering/monitoring/endpoints.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -173,7 +173,7 @@ A cluster member may still report `"isHealthy": true` even if the database curre
Not relevant to secondaries, and hence is not included.
| `raftCommandsPerSecond` label:deprecated[] | number | yes | `124` | An estimate of the average Raft state machine throughput over a sampling window configurable via `clustering.status_throughput_window` setting.
`raftCommandsPerSecond` is not an effective way to monitor that servers are not falling behind in updated and is hence deprecated and will be removed in the next major release of Neo4j.
It is recommended to use the metric `<prefix>.clustering.core.commit_index` on each server and look for divergence instead.
It is recommended to use the metric `<prefix>.cluster.raft.commit_index` on each server and look for divergence instead.
|===

After an instance has been switched on, the status endpoint can be accessed in order to make sure all the guarantees listed in the table below are met.
Expand Down