-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Added a REST API to List, Create, and Test rules #656
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
base: master
Are you sure you want to change the base?
Conversation
… merged fine though.
|
Cool idea! Also check your email @CCoffie :) |
|
This is awesome! Great job! 👍 |
|
This is a great addition and if combined with Backlog #420 would really bring a lot of power and flexibility to alerts. See untested fork here: |
|
@Qmando : Would love to know the answer to @kureus question. I've found no 'contributing' doc or similar to answer it myself. If there isn't one, I can file a separate issue and bring some common used template as a PR to work on it, if you feel it valuable. I'm interested on this REST feature, too since I am looking into adopting EA as a alerting solution and knowing such things would take out the uncertainity for us into investing into the tool and that would give peace of mind and clear the way to contributing, also. |
fixed double path /opt/elastalert/elastalert on linux user elastalert
Below are some changes I made to ElastAlert that add a REST API. I added this because I've been working on a kibana plugin that I'll hopefully be releasing soon that will allow for quick and easy management of ElastAlert Rules from directly within kibana. Figured I'd push these now though because it might help other out there that want to do something similar.