Adding ScyllaDB CPU usage graph + some other changes #3480
Merged
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
This was referenced Mar 5, 2025
This stack of pull requests is managed by Graphite. Learn more about stacking. |
ma2bd
approved these changes
Mar 5, 2025
ndr-ds
changed the base branch from
03-04-_benchmark_don_t_obliterate_validators_as_much_when_wrapping_up
to
graphite-base/3480
ndr-ds
force-pushed
the
03-05-adding_scylladb_cpu_usage_graph_some_other_changes
branch
from
aa39823 to
87cb69a
Compare
ndr-ds
force-pushed
the
graphite-base/3480
branch
from
a1b0081 to
b7e963a
Compare
ndr-ds
deleted the
03-05-adding_scylladb_cpu_usage_graph_some_other_changes
branch
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.
Motivation
I noticed we didn't have a ScyllaDB container CPU usage, and some of the JSON here seemed to be specific to Grafana Cloud.
Proposal
Add the ScyllaDB container CPU usage graph, and remove some stuff from the JSON
Test Plan
This was exported from a deployed network, so there shouldn't be any issues
Release Plan