You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/changes-deprecations-removals.adoc
+44-73Lines changed: 44 additions & 73 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -232,79 +232,50 @@ The `server.logs.config` and the `server.logs.user.config` are changed to depend
232
232
.See removed metrics in Neo4j 2025.01.
233
233
[%collapsible]
234
234
====
235
-
[options="header", cols="1,1"]
236
-
|===
237
-
|Name|Description
238
-
239
-
2+|**link:{neo4j-docs-base-uri}/operations-manual/5/monitoring/metrics/reference/#raft-core-metrics[Raft core metrics] - replaced accordingly by the link:{neo4j-docs-base-uri}/operations-manual/5/monitoring/metrics/reference/#raft-metrics[Raft metrics]**
240
-
241
-
|<prefix>.causal_clustering.core.append_index
242
-
|The append index of the Raft log. Each index represents a write transaction (possibly internal) proposed for commitment. The values mostly increase, but sometimes they can decrease as a consequence of leader changes. The append index should always be bigger than or equal to the commit index. (gauge)
243
-
|<prefix>.causal_clustering.core.commit_index
244
-
|The commit index of the Raft log. Represents the commitment of previously appended entries. Its value increases monotonically if you do not unbind the cluster state. The commit index should always be less than or equal to the append index and bigger than or equal to the applied index. (gauge)
245
-
|<prefix>.causal_clustering.core.applied_index
246
-
|The applied index of the Raft log. Represents the application of the committed Raft log entries to the database and internal state. The applied index should always be less than or equal to the commit index. The difference between this and the commit index can be used to monitor how up-to-date the follower database is. (gauge)
247
-
|<prefix>.causal_clustering.core.term
248
-
|The Raft Term of this server. It increases monotonically if you do not unbind the cluster state. (gauge)
249
-
|<prefix>.causal_clustering.core.tx_retries
250
-
|Transaction retries. (counter)
251
-
|<prefix>.causal_clustering.core.is_leader
252
-
|Is this server the leader? Track this for each Core cluster member. It will report 0 if it is not the leader and 1 if it is the leader. The sum of all of these should always be 1. However, there will be transient periods in which the sum can be more than 1 because more than one member thinks it is the leader. Action may be needed if the metric shows 0 for more than 30 seconds. (gauge)
|The highest transaction id that has been pulled in the last pull updates by this instance. (counter)
300
-
301
-
2+|**link:{neo4j-docs-base-uri}/operations-manual/5/monitoring/metrics/reference/#discovery-service-V1[Discovery metrics v1] - removed without replacement. See xref:monitoring/metrics/reference.adoc#discovery-service-metrics[Discovery metrics]**
302
-
|<prefix>.cluster.discovery.replicated_data|Size of replicated data structures. (gauge)
303
-
|<prefix>.cluster.discovery.cluster.members|Discovery cluster member size. (gauge)
|**link:{neo4j-docs-base-uri}/operations-manual/5/monitoring/metrics/reference/#raft-core-metrics[Raft core metrics] - replaced accordingly by the link:{neo4j-docs-base-uri}/operations-manual/5/monitoring/metrics/reference/#raft-metrics[Raft metrics]**
|**link:{neo4j-docs-base-uri}/operations-manual/5/monitoring/metrics/reference/#discovery-service-V1[Discovery metrics v1] - removed without replacement. See xref:monitoring/metrics/reference.adoc#discovery-service-metrics[Discovery metrics]**
0 commit comments