-
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
Problem with aggregation of Performance Counters within same category #4944
Comments
Would also love to hear any insight on this. FWIW, the documentation suggests an aggregation occurs also across categories (which is the desired behavior in almost every case I've seen): https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-metricset-windows-perfmon.html |
@synhershko Have a look at #6584 |
And the documentation that you linked to has been changed on master. https://www.elastic.co/guide/en/beats/metricbeat/master/metricbeat-metricset-windows-perfmon.html |
I'd absolutely love to see this. FWIW I would appreciate the ability to see an entire snapshot of the performance information inside one record though any aggregation is a win in my book. In my instance I'm using metricbeat to locate poor performing workstations. This means I'm often looking for a combination of CPU/Memory/Disk/Process stats at the same time. Looking at it from this aspect allows me to determine if the system is under powered or if a user is simply asking to much from the machine. |
Looks like there's a pull request that will resolve this: #8688 |
@githubmui, sounds like |
The text was updated successfully, but these errors were encountered: