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
Hey, thanks for the great project!
Newbie question, but how can I silent (or disable) the particular rule using swagger?
Any hint is appreciated 🙏
The text was updated successfully, but these errors were encountered:
Hi,
Currently there is no such method to do it in swagger.
You can try edit rule and add is_enabled to it.
is_enabled
https://elastalert2.readthedocs.io/en/latest/ruletypes.html
You can also delete rule and restore it later.
If you have access to elastic you add document to silence index directly. https://github.com/jertel/elastalert2/blob/master/elastalert/elastalert.py#L1778
silence
As a target solution, I would suggest add a new method in the API. Method should take two parameters
--rule
--silence
https://elastalert2.readthedocs.io/en/latest/flags.html
However, I won’t have time for this in the near future – a PR is always welcome! ;)
Note for dev purpose: https://github.com/jertel/elastalert2/pull/1004/files#r1018520966 @jertel was right. The behavior here will be differen. If someone uses only --silence, it will match by rule name, but with --silence_qk_value, it will match by realert_key.
--silence_qk_value
realert_key
Best regards, Mateusz
Sorry, something went wrong.
@Karql Thanks a lot! Will give it a try 👍
@ashliakhov johnsusek/elastalert-server only supports --silence. --silence_qk_value is not supported.
@Karql
Are there plans to support this in elastalert2-server?
No branches or pull requests
Hey, thanks for the great project!
Newbie question, but how can I silent (or disable) the particular rule using swagger?
Any hint is appreciated 🙏
The text was updated successfully, but these errors were encountered: