-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 fails to list all processes when run as a non-privileged user #12301
Labels
Comments
adriansr
added a commit
to adriansr/beats
that referenced
this issue
May 27, 2019
This updates vendored elastic/gosigar to v0.10.3, which addresses an issue when listing processes under a non-privileged Windows user. For the system/process metricset, only processes belonging to the user under which Metricbeat is running were reported. For the system/process_summary metricset, process belonging to other users were reported as unknown state. This fix will make Metricbeat able to report all processes, but information about which users owns those processes will be missing. Fixes elastic#12301
@narph I assigned you both after discussing the issue with @odacremolbap I had a quick fix for this in #12305, however, this PR is causing metricbeat to complain with an error after new code paths are being reached in the Windows+non-admin-user case:
This will make |
narph
added
Team:Integrations
Label for the Integrations team
[zube]: In Progress
labels
Jun 4, 2019
narph
added a commit
to narph/beats
that referenced
this issue
Jun 13, 2019
…#12475) * [Metricbeat] Fix system/process* metricsets under Windows This updates vendored elastic/gosigar to v0.10.3, which addresses an issue when listing processes under a non-privileged Windows user. For the system/process metricset, only processes belonging to the user under which Metricbeat is running were reported. For the system/process_summary metricset, process belonging to other users were reported as unknown state. This fix will make Metricbeat able to report all processes, but information about which users owns those processes will be missing. Fixes elastic#12301 * Added test func in order to provide more information on the failing match * Fix build error * Removed test func, correcting access rights in sigar_windows file (gosigar pr will follow), test only * Revert test changes, return debug message for process.getDetails * Replaced the PR number in the changelog * Adding selector to log debug message * Wrong type for pid in debug message (cherry picked from commit 08b5c38)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
When running Metricbeat under Windows as a regular, non-administrator user, the process / process_summary metricsets won't report processes belonging to other users.
The log is filled with messages like
The text was updated successfully, but these errors were encountered: