Skip to content

Commit 811ea1b

Browse files
Update content/vault/v1.20.x/content/partials/telemetry-metrics/vault/raft/thread/fsm/saturation.mdx
1 parent 7857e94 commit 811ea1b

File tree

1 file changed

+1
-2
lines changed
  • content/vault/v1.20.x/content/partials/telemetry-metrics/vault/raft/thread/fsm

1 file changed

+1
-2
lines changed

content/vault/v1.20.x/content/partials/telemetry-metrics/vault/raft/thread/fsm/saturation.mdx

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,5 +5,4 @@ Metric type | Value | Description
55
gauge | percentage | Approximate proportion of time the raft FSM goroutine could not accept new work
66

77
High saturation of the raft goroutines can increase latency in the rest of the
8-
system and cause cluster instability. We recommend a steady-state saturation
9-
less than 50%.
8+
system and cause cluster instability.

0 commit comments

Comments
 (0)