Open pmuellr opened 3 years ago
Pinging @elastic/kibana-alerting-services (Team:Alerting Services)
Hello,
we had the same issue and need solution on ECE 2.13.1 with Kibana 7.17.1 and wait on better view what's going on.
how to resolve ?
regards, Matthias
Currently the alerting health reporting only sends a status "level" value up to Kibana's plugin status infrastructure. Those values are
unavailable
,degraded
, .... However the plugin status infrastructure also allows a "summary" (string) of that status to also be sent. If it's not sent in, Kibana uses a generic summary like "Alerting framework is degraded".Throughout both alerting and task manager code, there's some infrastructure for passing these status levels around, but we really need to change WHAT we're passing to be both the level and summary, instead of just the level. Since it doesn't pass a summary now, we always see the generic message.
Here's an example of where we set the alerting HealthStatus to
Warning
, which will end up setting the Kibana status level todegraded
. We should also be creating the string for the "summary" field here.https://github.com/elastic/kibana/blob/dd3053d23e99de1ba8e58608ffecebd0d6b2638c/x-pack/plugins/alerting/server/health/get_health.ts#L40-L45
As mentioned ^^^ task manager has a very similar structure to alerting regarding setting these status values, and so needs a similar change.