-
Notifications
You must be signed in to change notification settings - Fork 119
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
Is that project ended? #151
Comments
It seems yes |
No response from project officials |
Kibana 6.8.1-6.8.9, 7.5.1, 7.5.2, 7.6.0-7.7.0 will be supported by me until the official official support! If you have any problems, please give us your feedback. There are a certain number of people who don't want to go into the server and edit yaml directly, and that it's fine from the browser. Praeco doesn't have much support for alert recipients, so even if you suggest it, it's rejected, so some people want to use elastalert-kibana-plugin. Personally, there are places where I would like to change the operation of Praeco's alert notification destination. |
Great @nsano-rururu |
■ What you cannot know at this moment ・ElastAlert's alert rule directory cannot be edited/deleted from the screen even if a directory is created directly below and the alert rule file is placed in the created directory. Is the management target only under the alert rule directory? ・Not compatible with alert rule templates ・Silence settings for alert rules ・Enable/disable alert rules ・Kibana setting does not work even if you change the background color ■Bug? ・If an alert rule with the same name already exists and you create it with the same alert rule name, the content of the alert rule created later will be overwritten. |
Kibana 6.8.10, 7.7.1, 7.8.0 are also supported |
??
The text was updated successfully, but these errors were encountered: