Skip to content
New issue

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

Migration of existing Watcher alerts to Alerting Framework #40505

Closed
6 tasks
cachedout opened this issue Jul 8, 2019 · 1 comment
Closed
6 tasks

Migration of existing Watcher alerts to Alerting Framework #40505

cachedout opened this issue Jul 8, 2019 · 1 comment
Assignees
Labels
enhancement New value added to drive a business result Meta Team:Monitoring Stack Monitoring team

Comments

@cachedout
Copy link
Contributor

Current State

At present, Stack Monitoring has six alerts which ship with the application. These are as follows:

  1. Cluster status

  2. Nodes changed

  3. Elasticsearch version mismatch

  4. Kibana version mismatch

  5. Logstash version mismatch

  6. 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.

  1. Cluster status
  2. Nodes changed
  3. Elasticsearch version mismatch
  4. Kibana version mismatch
  5. Logstash version mismatch
  6. License expiration

cc: @elastic/stack-monitoring

@cachedout cachedout added Meta enhancement New value added to drive a business result Team:Monitoring Stack Monitoring team labels Jul 8, 2019
@cachedout
Copy link
Contributor Author

Closing in favor of a meta-issue elsewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Meta Team:Monitoring Stack Monitoring team
Projects
None yet
Development

No branches or pull requests

2 participants