Describe the feature:
The metricbeat module "elasticsearch" ships the thread pool statistics either with a new or existing metricset (node/cluster level). Data arrives in the metricbeat-* index.
Describe a specific use case for the feature:
We would like to monitor the thread pool stats in custom dashboards using the metricbeat "elasticseach" module (Elasticsearch: ET /_nodes/stats/thread_pool).
Problem with existing implementation:
None of the Metricbeat metricsets of the module "elasticsearch" delivers the thread pool statistics.
Using the module "elasticsearch-xpack" module, generates the thread pool statistics (and all the other data) to the .monitoring-es* index, which is under control of ES/Kibana. The amount of data is huge, metricset filter cannot be applied.
Describe the feature: The metricbeat module "elasticsearch" ships the thread pool statistics either with a new or existing metricset (node/cluster level). Data arrives in the metricbeat-* index.
Describe a specific use case for the feature: We would like to monitor the thread pool stats in custom dashboards using the metricbeat "elasticseach" module (Elasticsearch: ET /_nodes/stats/thread_pool).
Problem with existing implementation: