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

Use max in k8s overview dashboard aggregations #17015

Merged
merged 1 commit into from
Mar 17, 2020

Conversation

ChrsMark
Copy link
Member

What does this PR do?

Changes types of aggregations from sum to max on the following visualisations of Kubernetes Overview:

  • Network in by node [Metricbeat Kubernetes] ECS
  • Network out by node [Metricbeat Kubernetes] ECS
  • Top CPU intensive pods [Metricbeat Kubernetes] ECS

Why is it important?

We should not be using a sum on kubernetes.pod.network.rx.bytes,
kubernetes.pod.network.tx.bytes, and kubernetes.container.cpu.usage.core.ns;
these fields are counters.
https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/apis/stats/v1alpha1/types.go#L165
https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/apis/stats/v1alpha1/types.go#L198
We should use max instead.

Related issues

Screenshots

Screenshot 2020-03-16 at 11 40 00
Screenshot 2020-03-16 at 11 39 39

We should not be using a sum on kubernetes.pod.network.rx.bytes,
kubernetes.pod.network.tx.bytes, and kubernetes.container.cpu.usage.core.ns;
these fields are counters.

Signed-off-by: chrismark <[email protected]>
@ChrsMark ChrsMark added bug review :Dashboards containers Related to containers use case [zube]: In Review v7.7.0 Team:Platforms Label for the Integrations - Platforms team labels Mar 16, 2020
@ChrsMark ChrsMark self-assigned this Mar 16, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations-platforms (Team:Platforms)

@ChrsMark ChrsMark requested a review from a team March 16, 2020 10:11
@ChrsMark ChrsMark added the needs_backport PR is waiting to be backported to other branches. label Mar 16, 2020
@ChrsMark ChrsMark requested a review from a team March 16, 2020 12:18
Copy link
Contributor

@blakerouse blakerouse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

@ChrsMark ChrsMark merged commit 0a2b3f4 into elastic:master Mar 17, 2020
ChrsMark added a commit to ChrsMark/beats that referenced this pull request Mar 17, 2020
We should not be using a sum on kubernetes.pod.network.rx.bytes,
kubernetes.pod.network.tx.bytes, and kubernetes.container.cpu.usage.core.ns;
these fields are counters.


(cherry picked from commit 0a2b3f4)
@ChrsMark ChrsMark removed the needs_backport PR is waiting to be backported to other branches. label Mar 17, 2020
ChrsMark added a commit that referenced this pull request Mar 18, 2020
We should not be using a sum on kubernetes.pod.network.rx.bytes,
kubernetes.pod.network.tx.bytes, and kubernetes.container.cpu.usage.core.ns;
these fields are counters.


(cherry picked from commit 0a2b3f4)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug containers Related to containers use case :Dashboards review Team:Platforms Label for the Integrations - Platforms team v7.7.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Kubernetes Overview dashboard using wrong aggregations
4 participants