release-22.2: kvserver: add storage time-series metrics for level size and score #88592
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.
Backport 1/1 commits from #88504 on behalf of @nicktrav.
/cc @cockroachdb/release
Currently, the only way to infer the compaction score and heuristics is to use the LSM printout from the logs (emitted once every ten minutes), or to call the
/debug/lsm
endpoint manually, and track values over time. This makes it difficult to debug issues retroactively.Add two new sets of per-LSM-level time-series metrics for level size and level score. These new metrics have names of the form
storage.$LEVEL-level-{size,score}
.Closes #88415.
Release note (ops change): Adds two new sets of per-LSM-level time-series metrics, one for level size and another for level score. These metrics are of the form
storage.$LEVEL-level-{size,score}
.Release justification: Low risk, high benefit changes to existing functionality.