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

Cache values missing in Memory Usage [Metricbeat System] Visualization #5706

Closed
ajpahl1008 opened this issue Nov 24, 2017 · 3 comments
Closed
Labels

Comments

@ajpahl1008
Copy link

ajpahl1008 commented Nov 24, 2017

  • Version: 6.0.0

  • Operating System: Ubuntu Linux 17.10

  • Steps to Reproduce:

    Setting up the default metricbeat via -setup argument, the graph for Memory usage shows 0.0B of cache used. The operating system's "free" and "nmon" show significant usage (~18GB).

brokengraph

free_output

nmon_output

To see cache I modified the aggregation in the cache series
from
system.memory.actual.used bytes
to
system.memory.actual.free

config_change_made

And I could begin to see cache statistics in the graph.

fixedgraph

@ajpahl1008
Copy link
Author

Created branch
https://github.com/elastic/beats/tree/metricbeats_cache_fix

Going to attempt to test it locally before putting a merge request in.

@ruflin
Copy link
Contributor

ruflin commented Nov 26, 2017

Not sure if that could also be related? elastic/gosigar#82

@andrewkroh andrewkroh added Metricbeat Metricbeat bug and removed Metricbeat Metricbeat labels Sep 18, 2018
@andrewkroh
Copy link
Member

This appears to have been fixed since this was opened. This was taken from a Metricbeat 6.3.1 env.

screen shot 2018-09-18 at 6 49 29 pm

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

No branches or pull requests

3 participants