-
Notifications
You must be signed in to change notification settings - Fork 88
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
Future Support for Elastalert API? #218
Comments
About OSS Manuals may not be organized |
Praeco uses ElastAlert Server, which is a fork of Bitsensor. Customization, bug fixes, ElastAlert 0.2.4 support, library updates, etc. Although there are some issues that require replacement of deprecated libraries (request and request-promise-native) johnsusek/elastalert-server (DockerHub) |
I'm not an admin so I can't answer about Future Support. I answered only what I can answer. |
Thanks. That's pretty much what I already figured. I probably should have posted this in the Elastalert Server fork since it's more related to the future of that build. Figured there wouldn't be any concrete answers, but wanted to double check if there had been any talk about how that will be handled. There's always some uncertainty with OSS software, but with Bitsensor gone the future of Elastalert Server is especially uncertain. Guess we'll just have to weigh our options and hope for the best if we do end up using Praeco. Thanks. |
Changed node.js to typescript based on Bitsensor's elastalert-server. If you want to use the full functionality of elastalert2, consider using elastalert2 directly. |
From this comment, it looks like Bitsensor went under and is no longer going to be maintaining Elastalert API.
Have you heard anything about how it will continue to be updated going down the line? I want to spend some more time trying to get this up and running in our kubernetes cluster, but the uncertainty of future support for the API is concerning.
The text was updated successfully, but these errors were encountered: