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

Improve error handling when collecting processes information #9111

Closed
jsoriano opened this issue Nov 15, 2018 · 2 comments
Closed

Improve error handling when collecting processes information #9111

jsoriano opened this issue Nov 15, 2018 · 2 comments

Comments

@jsoriano
Copy link
Member

jsoriano commented Nov 15, 2018

Process information is collected non-atomically, so it can be possible that processes finish while metricbeat is collecting its metrics, provoking failures as the process is not found.
If something fails when collecting process information, whole events are lost, and errors are logged.

We could ignore the errors in some cases, reducing events loss.

We can also evaluate to use go-sysinfo instead of gosigar for processes info collection, at least on windows where it should be faster as mentioned in elastic/gosigar#110 (review)

@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
@jsoriano jsoriano removed the Stalled label Jul 9, 2020
@botelastic
Copy link

botelastic bot commented Jun 9, 2021

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.

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

No branches or pull requests

3 participants