You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some newer features such as ES|QL (esql_worker) and intra-segment search parallelism (search_worker) have been introduced in 8.x and Metricbeat monitoring isn't capturing the relevant thread pools yet.
The average service time can also be helpful, for example the write time per document or query time per search. This is usually just a simple division like indices.write.time_in_millis / indices.write.total, but if it is calculated at ingest time, it is possible to sort by this metric in visualizations.
The text was updated successfully, but these errors were encountered:
Metricbeat (as of 8.15.3) used for stack monitoring collection is still missing some helpful metrics for building comprehensive monitoring dashboards.
Here is a potential list of metrics to included from
_node/stats
:Some newer features such as ES|QL (
esql_worker
) and intra-segment search parallelism (search_worker
) have been introduced in 8.x and Metricbeat monitoring isn't capturing the relevant thread pools yet.The average service time can also be helpful, for example the
write
time per document orquery
time per search. This is usually just a simple division likeindices.write.time_in_millis / indices.write.total
, but if it is calculated at ingest time, it is possible to sort by this metric in visualizations.The text was updated successfully, but these errors were encountered: