helm: Add CPU panel to Hubble L7 HTTP Workload dashboard #24934
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
chancez
added
kind/enhancement
maintainer-s-little-helper
bot
added
the
dont-merge/needs-release-note-label
chancez
force-pushed
the
pr/chancez/hubble_l7_dashboard_cpu_panel
branch
from
65356a2
to
012de47
Compare
CPU load is can be help to diagnose changes in request latency, so add a CPU panel next to the HTTP request duration panel. Signed-off-by: Chance Zibolski <chance.zibolski@gmail.com>
chancez
force-pushed
the
pr/chancez/hubble_l7_dashboard_cpu_panel
branch
from
012de47
to
89c2dd1
Compare
squeed
approved these changes
Apr 18, 2023
chancez
added
the
release-note/minor
maintainer-s-little-helper
bot
removed
the
dont-merge/needs-release-note-label
chancez
added
the
ready-to-merge
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.
CPU load is can be help to diagnose changes in request latency, so add a CPU panel next to the HTTP request duration panel.
This does use a recording rule metric
node_namespace_pod_container:container_cpu_usage_seconds_total:sum_irateandnamespace_workload_pod:kube_pod_owner:relabelfrom kube-prometheus. If a user is not using kube-prometheus, then they can copy the recording rule into their installation if they do not already have it.Here's what the new panel looks like. There is also one in the row below for CPU utilization by destination.