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

[Metricbeat] kubernetes.container.memory.available.bytes should default to the system allocatable memory. #6125

Closed
simianhacker opened this issue Jan 19, 2018 · 0 comments · Fixed by #6158
Labels
Metricbeat Metricbeat

Comments

@simianhacker
Copy link
Member

When admins don't set kubernetes.container.memory.available.bytes it should default to kubernetes.node.memory.allocatable.bytes

@simianhacker simianhacker added the Metricbeat Metricbeat label Jan 19, 2018
ruflin pushed a commit that referenced this issue Jan 28, 2018
…#6158)

This PR adds the following set of calculated metrics for Pods and containers:

- `kubernetes.container.cpu.usage.node.pct`
- `kubernetes.container.cpu.usage.limit.pct`
- `kubernetes.container.memory.usage.node.pct`
- `kubernetes.container.memory.usage.limit.pct`
- `kubernetes.pod.cpu.usage.nanocores`
- `kubernetes.pod.cpu.usage.node.pct`
- `kubernetes.pod.cpu.usage.limit.pct`
- `kubernetes.pod.memory.usage.bytes`
- `kubernetes.pod.memory.usage.node.pct`
- `kubernetes.pod.memory.usage.limit.pct`

As the source of data to calculate these values comes from different places (kubelet & kube-state-metrics) I added a mechanism to share some performance metrics through an in-memory cache. For that reason, these new metrics will only be available when `state_*` metricsets are enabled.

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

Successfully merging a pull request may close this issue.

1 participant