Thread pool stats in .monitoring-es* indices

Hi Folks

Noticed that the elasticsearch built-in (and metricbeat) monitoring doesn't capture all the thread pool stats, it only captures queue size, rejected count and current threads (pool size, which usually stays the same)

Queue and rejected are useful if you are constrained by thread pool sizes, but we are not, but would still like to see how busy each node is, so why not capture the active count?

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.