Yesterday I observed when running a large number of alerting rules that there were logs mentioning Kibana was unhealthy while it wasn't the case. After looking into it, I noticed the health report doesn't observe more than a single Kibana node at any given time. Turns out it's because of the ownerId aggregation on the tasks index, which filters for startedAt to be within a given time range but this field is no longer mapped. We should look into fixing this so we don't continue to generate false reports for customers. https://github.com/elastic/kibana/blob/9accb33d18c4828f6141a4b9299b8ec29f0e28df/x-pack/plugins/task_manager/server/monitoring/workload_statistics.ts#L166-L169
Yesterday I observed when running a large number of alerting rules that there were logs mentioning Kibana was unhealthy while it wasn't the case. After looking into it, I noticed the health report doesn't observe more than a single Kibana node at any given time. Turns out it's because of the ownerId aggregation on the tasks index, which filters for
startedAt
to be within a given time range but this field is no longer mapped. We should look into fixing this so we don't continue to generate false reports for customers. https://github.com/elastic/kibana/blob/9accb33d18c4828f6141a4b9299b8ec29f0e28df/x-pack/plugins/task_manager/server/monitoring/workload_statistics.ts#L166-L169