metricbeat cgroup memory reporting isn't quite correct #6033
Labels
Comments
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this issue
Jan 9, 2018
The mem values were being reported for the memsw, kmem, and kmem_tcp values. Fixes elastic#6033
|
I have opened a PR to fix this at #6034. |
exekias
pushed a commit
that referenced
this issue
Jan 10, 2018
The mem values were being reported for the memsw, kmem, and kmem_tcp values. Fixes #6033
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this issue
Jan 10, 2018
The mem values were being reported for the memsw, kmem, and kmem_tcp values. Fixes elastic#6033 (cherry picked from commit 49f6a19)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would appear the memsw/kmem reporting for cgroups isn't being reported correctly & after a discussion with @andrewkroh it seems to originate from
https://github.com/elastic/beats/blob/master/metricbeat/module/system/process/cgroup.go#L120
where it's not using the local
datavariable, so all mem/memsw/kmem reporting is just usingmemory.Memcounters.The text was updated successfully, but these errors were encountered: