Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix issues in Compute Resource network panels #284

Merged
merged 4 commits into from
Oct 28, 2019

Conversation

dghubble
Copy link
Contributor

@dghubble dghubble commented Oct 27, 2019

  • Fix Compute Resource networking panels to filter by $cluster. This is important when showMultiCluster=true, bc the network panels are causing fanout to all clusters, erroneously showing an aggregate across all (CPU and mem do not), and may load many pods in tables (slow)
  • Fix "Compute Resources / Workload" network panels to respect the $workload filter
  • Fix "Compute Resources / Namespace (Workloads)" to use $datasource instead of a hardcoded "prometheus". Also fix CPU and memory panels to filter based on workload type

Related: #248

* Fix Compute Resource dashboard networking panels to
filter by $cluster, like for CPU and Memory panels. This
is important when showMultiCluster=true bc the network
panels are causing fanout to all clusters, erroneously
aggregating across all of them, and may load a quite
large number of pods into tables (slow)

Rel: kubernetes-monitoring#248
* Fix network panels in the "Compute Resources / Workload"
dashboard to respect the selected "$workload" like CPU and
memory panels
* Previously, "Compute Resources / Namespace (Workloads)"
dashboard was missing a workload "$type" template variable,
if there was no datasource called "prometheus" causing a
warning to be shown
* Template the workload type's datasource as '$datasource'
* Fix CPU and memory panels to filter using the type
@dghubble
Copy link
Contributor Author

I can file these 3 fixes separately if desired. Note, the "Kubernetes / Networking" dashboards seem to have similar problems, but I've not used or fixed those

* Add $cluster filter to the "Compute Resources / Workload"
network usage table
@dghubble dghubble changed the title Fix various bugs in compute resource network panels Fix issues in Compute Resource network panels Oct 27, 2019
@metalmatze
Copy link
Member

Nice!
Maybe someone else wants to update the Kubernetes / Networking dashboard?!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants