We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
At present, Stack Monitoring has six alerts which ship with the application. These are as follows:
Cluster status
Nodes changed
Elasticsearch version mismatch
Kibana version mismatch
Logstash version mismatch
License expiration
As one can plainly see, these are defined and shipped with Elasticsearch and use the Watcher framework.
The Kibana team is rapidly developing a new alerting framework. .
We want to take our existing watches and migrate them to the new framework. This issue serves as a meta-issue to track the progress of that effort.
cc: @elastic/stack-monitoring
The text was updated successfully, but these errors were encountered:
Closing in favor of a meta-issue elsewhere.
Sorry, something went wrong.
chrisronline
No branches or pull requests
Current State
At present, Stack Monitoring has six alerts which ship with the application. These are as follows:
Cluster status
Nodes changed
Elasticsearch version mismatch
Kibana version mismatch
Logstash version mismatch
License expiration
As one can plainly see, these are defined and shipped with Elasticsearch and use the Watcher framework.
Desired State
The Kibana team is rapidly developing a new alerting framework. .
We want to take our existing watches and migrate them to the new framework. This issue serves as a meta-issue to track the progress of that effort.
cc: @elastic/stack-monitoring
The text was updated successfully, but these errors were encountered: