Open stefnestor opened 2 years ago
Pinging @elastic/kibana-docs (Team:Docs)
I'm not against this, but one of the problems is that as the alerting documents / indices change over time, this information is going to become out of date. OTOH, over time, I'd expect our monitoring of alerting within the product itself is going to get a lot better and the need for these low-level searches won't be generally needed.
Perhaps we could take the queries we plan on talking about, and build tests for them (functional tests), noting in the test that if they fail, the doc will also need to be updated.
Is there anything similar in the Kibana docs, to get a sense for how others have dealt with this kind of stuff?
Perhaps we could take the queries we plan on talking about, and build tests for them (functional tests), noting in the test that if they fail, the doc will also need to be updated. Is there anything similar in the Kibana docs, to get a sense for how others have dealt with this kind of stuff?
@elastic/kibana-docs can you speak to this?
My comment ^^^ is basically blue-sky. We can get by for quite some time without it, of course.
đź‘‹ So we've written a related blog (only change was adding a *
on .kibana
). IMO there's still appetite for this from customers. Could we reconsider porting the above content / blog into Kibana Troubleshooting docs?
👋🏼 @KOTungseth @gchaps adding placeholder from our conversation about copying over my Medium article about monitoring Kibana Rules so Dev can confirm/review. @pmuellr @gmmorris,