Please don't let this die. ElastAlert usecase is very strong.

[nickbabkin]

Sorry for being repetitive but I wanted to emphasize this.

@Qmando I've heard you are divorcing with the project, so that wanted to ask you to not let this gem of a software simply die.

Usecase for ElastAlert is pretty unique and it stands well in the ELK ecosystem as an open source alternative to licensed Elastic alerting features. Moreover, the functionality is way way richer than what Elastic guys have under the hood as of August 2020.

You did a great job with building and maintaining it, now please hand it over to someone who deserves.

Cheers!

[ManuelFFF]

Hi @nsano-rururu ,

I would like to know:

1. I have never used Docker before. Does this work like a VM inside Linux?
2. Would Praeco do the same work (or similar) that ElastAlert Kibana Plugin does?
3. I have Nginx running on the same server where I would install Praeco. Would that be an issue or create a conflict with other apps needing Nginx in the server.

Thank you

[mrfroggg]

I think that @nsano-rururu should be made an admin on this project (if you agree!), as he seems to be active on the dev side!

@Qmando, that would be great to grant the admin rights to other devs, as the development of this project could continue!

Also, I would suggest to open a Google Groups for all user questions and problems, close them in the Github Issues as it's hard to fellow what is a dev issue and what is a user question and only allow dev Issues in here! A good cleanup would be a good idea!

[Qmando]

Hi. Sorry that this has remained dormant for quite a while and the PR/issues have gotten completely out of hand.

We do plan on handing the project over to new maintainers, stay tuned. I'll try to get that ball rolling on that before the end of the year.

[abhishek-jaisingh]

@mrfroggg we already have a Gitter channel for the same: https://gitter.im/Yelp/elastalert

[abhishek-jaisingh]

@Qmando I understand that the project may be too big for a single maintainer to keep working on (even harder if its just a part-time work). It'll be better if you can assign ownership to more than one person (who is active on the project) so as the issues are resolved & addressed quickly and a single person doesn't become a bottleneck for the same.

[immanuelfodor]

I'm really interested in how the maintenance handover or involvement turns out, it's almost EOY (#2947 (comment)), and @nsano-rururu seems to be all over into EA based on his Github activity across multiple projects, so I think it would be in good hands.

Reference for other similar issues without existing connection to this one: #2946, #2911

[immanuelfodor]

There are still a few days until the year ends, let's hope for the best.

[devdua]

@nsano-rururu I also believe strongly in this project and would be willing to be a maintainer/contributor

[mrfroggg]

I think we have 2 options:

• Check with Yelp (Github root of this project) to add new maintainers to Elastalert
• If no answer from Yelp, create an official fork to continue Elastalert's development on another github repo.

[devdua]

I think we should wait until next week as most employees are on vacation during this time. I agree with @mrfroggg on both options.

[immanuelfodor]

As much as I would like somebody to take over active development of ElastAlert, I think the current situation and way of communication leaves a bad taste, it's just not that professional as it could be, almost hostile. I understand the accumulated frustration here but we shouldn't give up maintaining a communication style that is not harmful for other human beings and the project itself. What @mrfroggg suggested, is totally reasonable, we either ask the team behind the project (nicely) that here are some devs that are worthy of being new maintainers, or just create an official fork, and merge the PRs there, comment on all issues that reopen them there, etc.

[devdua]

Hi @Qmando, Happy New Year! Is there a plan to hand over this project? There are a few people here who would definitely like to be maintainers.