-
Notifications
You must be signed in to change notification settings - Fork 257
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
kapacitor rules [tasks] disable option #847
Comments
@chetu thanks for writing in and absolutely we need to do this! |
Yes, it will be very useful for us as well. Also I want to have the ability to write some comments when I disable tasks or I wan`t to disable it for some time (it should be automatically enabled after some time) |
@alyan2008 I agree that recording comments about alerts is important. @nathanielc does kapacitor have facilities for adding "notes" to a task? I don't see anything in the API (https://github.com/influxdata/kapacitor/blob/master/client/API.md#tasks). |
@goller No it does not. Slightly related we do plan to add a silence feature to Kapacitor that would allow you to silence individual alerts without needing to disable the entire task. That feature would accept "notes" about why an alert was silenced. Although there is some overlap here so we should make sure the use case is clear. |
Hi @chetu and @alyan2008, @121watts and I have PR #868 up that implements disabling and enabling of the alerts. We are hoping to get it merged in for today's release! |
We were able to get the disable/enable into 1.2.0-beta2 release yesterday. @alexpaxton styled it like this on the alerts page: Try it out! |
Hey guys, it doesn't work when you have more then 1 alert. |
@alekseyp Just reproduced this. Expect a hotfix soon. |
Need to option to mute kapacitor tasks from chronograf UI.
Right now we have to do it from kapacitor cli :
The requirement to mute rules is required when we plan downtime/maintenance to production servers and avoid all alerts during maintenance period.
The text was updated successfully, but these errors were encountered: