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

Continuation of: Adriansr fix mb windows procs #12301 (#12475) #12527

Closed
wants to merge 1 commit into from

Conversation

narph
Copy link
Contributor

@narph narph commented Jun 13, 2019

Backport to 7.2 #12475 (comment)

  • [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 #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)

…#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)
@narph narph added the backport label Jun 13, 2019
@narph narph requested a review from a team as a code owner June 13, 2019 09:50
@narph narph requested a review from adriansr June 13, 2019 09:50
@narph narph self-assigned this Jun 13, 2019
@narph narph added Team:Integrations Label for the Integrations team :Windows labels Jun 13, 2019
Copy link
Contributor

@adriansr adriansr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For backports we use the script under dev-tools/cherrypick_pr, which creates the PR for you (right now seems that it's broken).

It's better if you stick to the format that it creates:
title: Cherry-pick #NNNN to 7.X: {original title}
message:
Cherry-pick of PR #NNNN to 7.X branch. Original message:
{original message}

@@ -134,6 +134,8 @@ https://github.com/elastic/beats/compare/v7.0.0-alpha2...master[Check the HEAD d
- Fixed RabbitMQ `queue` metricset gathering when `consumer_utilisation` is set empty at the metrics source {pull}12089[12089]
- Fix direction of incoming IPv6 sockets. {pull}12248[12248]
- Ignore prometheus metrics when their values are NaN or Inf. {pull}12084[12084] {issue}10849[10849]
- In the kibana/stats metricset, only log error (don't also index it) if xpack is enabled. {pull}12265[12265]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This changelog entry sneaked in. Happens frequently with backports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Team:Integrations Label for the Integrations team :Windows
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants