-
Notifications
You must be signed in to change notification settings - Fork 796
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
Add gauge for total fields mapped in an index #257
Comments
Hi James, thanks for the feature proposal. I'm not sure if this a feature the majority of our users would benefit from. In general we are trying to focus on the ES operational metrics (as compared to the content related metrics). The above use case has clearly a bit of both. What would be the underlying API call to get the number of fields mapped in an index? maybe we are already doing the call and are just not exposing the result as a metric? |
I don't think there is an underlying API to get this number directly - you have to get the mapping data from the index API and count the fields. I might be wrong about that though. (EDIT: and there will be plenty of edge cases there, eg when you have a text field with a subfield you'll have to count that twice ... ) |
The metric would be very helpful for us too (e.g. we haven't noticed the increase in mapped fields) which now results in a very poor Kibana UI performance |
May someone review #364 ? |
Signed-off-by: Mike Roest <[email protected]>
* #257: Add gauge for total fields mapped in an index Signed-off-by: Mike Roest <[email protected]> Co-authored-by: Marco Sohns <[email protected]> Co-authored-by: Jeff Nadler <[email protected]>
* prometheus-community#257: Add gauge for total fields mapped in an index Signed-off-by: Mike Roest <[email protected]> Co-authored-by: Marco Sohns <[email protected]> Co-authored-by: Jeff Nadler <[email protected]> Signed-off-by: Toomas Ormisson <[email protected]>
* prometheus-community#257: Add gauge for total fields mapped in an index Signed-off-by: Mike Roest <[email protected]> Co-authored-by: Marco Sohns <[email protected]> Co-authored-by: Jeff Nadler <[email protected]>
Motivation: ES imposes a limit on the number of fields mapped, and we'd like to alert when we're approaching that limit. We've got a lot of custom ELK tooling and suchlike, so there's the potential for a bug to flood the index with new fields, for example.
Happy to bring a PR if it is thought to be useful!
The text was updated successfully, but these errors were encountered: