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] Collect Working Set Size memory metric on Linux #9859

Closed
geekpete opened this issue Jan 3, 2019 · 1 comment
Closed

[Metricbeat] Collect Working Set Size memory metric on Linux #9859

geekpete opened this issue Jan 3, 2019 · 1 comment
Labels

Comments

@geekpete
Copy link
Member

geekpete commented Jan 3, 2019

Describe the enhancement:

Add WSS (Working Set Size) to the linux process metricset in metricbeat.
This might require work to the underlying GoSigar library to add this capability.

Describe a specific use case for the enhancement or feature:

Provides more visibility/detail with memory usage on Linux, useful to know for capacity planning and scalability analysis of your processes.

Methods to collect WSS on Linux:
http://www.brendangregg.com/wss.html

Seems already present for Windows in the gosigar library but not for Linux:
https://github.com/elastic/gosigar/blob/master/sys/windows/syscall_windows.go#L119-L134
https://github.com/cloudfoundry/gosigar/search?q=WorkingSetSize&type=Code&utf8=%E2%9C%93

Loosely related:
#8345

@geekpete geekpete changed the title Collect Working Set Size memory metric on Linux [Metricbeat] Collect Working Set Size memory metric on Linux Jan 3, 2019
@ruflin ruflin added module Team:Integrations Label for the Integrations team labels Jan 7, 2019
@botelastic
Copy link

botelastic bot commented Jul 8, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@botelastic botelastic bot added the Stalled label Jul 8, 2020
@botelastic botelastic bot closed this as completed Aug 7, 2020
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

2 participants