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

Perfmon should generate unified static layout events for each performance monitor #12262

Closed
vbohata opened this issue May 23, 2019 · 3 comments
Closed
Labels

Comments

@vbohata
Copy link

vbohata commented May 23, 2019

I think the best would be to generate single event per performance counter value and use pre-defined field names so the result could look like this:
{
"windows": {
"perfmon": {
"category" : ".NET CLR Exceptions",
"instance" : "??APP_CLR_PROC??",
"name" : "my_counter_name",
"value" : 0.0
}
}
}

There are many advantages:

  1. Allows term aggregations per category, name ...
  2. Allows easy filtering results for known category, name, ... No need for searching available fields.
  3. Avoids possible huge number of dynamic fields.
  4. With a little modification can be part of the ECS.
  5. In environments/companies with mix of metricbeat, 3rd party and custom log shippers allows easily mixing the data searching via Kibana.

Our use case: large number of teams, some of them managing metricbeat configuration by themselves. Large number of perfcounters. Each new counter requires us to refresh the Kibana index pattern mapping, also it is not possible to find the perfcounter by name, ...

I also commented it here:
#6584 (comment)

@narph
Copy link
Contributor

narph commented Apr 21, 2020

@vbohata , although this is a year long issue, you might want to have a look at #17596, as it satisfies most of your requests, let us know what you think.

@vbohata
Copy link
Author

vbohata commented May 4, 2020

Looks definitely better.

Pros:

  • can be queried much better
  • is compact

Cons:

  • can not do aggregations on metrics names to return values like "time_processor_pct"

@narph narph removed their assignment Oct 25, 2021
@botelastic
Copy link

botelastic bot commented Oct 25, 2022

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

@botelastic botelastic bot added the Stalled label Oct 25, 2022
@botelastic botelastic bot closed this as completed Apr 23, 2023
@zube zube bot removed the [zube]: Done label Jul 23, 2023
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

4 participants