Add storage.wal.fsync.latency and other metrics
#19425
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Files changed:
|
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify site configuration. |
rmloveland
force-pushed
the
20250306-DOC-11996-storage-essential-metrics
branch
from
2392785 to
5d8469e
Compare
rmloveland
changed the title
storage.wal.fsync.latency to metricsstorage.wal.fsync.latency and other metrics
Fixes DOC-11996 Adds the following metrics to the docs: - storage.wal.fsync.latency - rebalancing.range.rebalances - rebalancing.replicas.queriespersecond
rmloveland
force-pushed
the
20250306-DOC-11996-storage-essential-metrics
branch
from
5d8469e to
78c6838
Compare
rmloveland
commented
Mar 10, 2025
kvoli
reviewed
Mar 13, 2025
kvoli
approved these changes
Mar 18, 2025
jbowens
approved these changes
Apr 8, 2025
There was a problem hiding this comment.
lgtm
seconding @sumeerbhola's slack comment that maybe we should update the WAL failover page to reference storage.wal.failover.write_and_sync.latency. The tl;dr is that storage.wal.fsync.latency monitors the latencies of WAL files. If you have WAL failover enabled and are failing over, storage.wal.fsync.latency will include the latency of the stalled primary. The storage.wal.failover.write_and_sync.latency metric is up one level, and during the failover will report the latency actually observed by higher-levels (which should be ~equivalent to the latency of the secondary).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes DOC-11996