-
Notifications
You must be signed in to change notification settings - Fork 783
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
Project Dead #349
Comments
Hey, not really dead, but in fact there hasn't been much work from my side. Too busy with other projects :( The next steps I thought of are:
It's really on my list to give this project some love. Sorry if this hasn't happened lately |
@zwopir I can help with that :) Been keeping my own fork for some time (eventually swiching back to the main one when changes get out), can also do the CI pipeline et al (I maintain goreleaser and have some exporters using it to release, can do that if you are into it)... Anyway, the company I work for use this a lot, so I'm up to help maintaining it 👌 |
Another approach is to move the repo to prometheus-community. https://github.com/prometheus-community We would then switch to the prometheus CI / build tools (promtool). I could sponsor that move as I am a user of this exporter. |
Sounds good too! Happy to help maintaining it anyway :) |
We use this component extensively as well internally. Have been considering adding CCS (Cross cluster search) metrics collections as a PR. Happy to contribute in part also perhaps, but community adoption seems most sensible. |
sidenote for the sake of clarity: I just open some PRs/issues here, I'm not an official contributor (although I would be happy to be). |
Ack, I was mislead by the first comment. If the repo is transferred, you will be on the team. It is @zwopir 's call to transfer or not the repository. If they have issue with it, they can comment here and we can further tune this. |
yeah, I figured, sorry about it...
ack 👍 |
@roidelapluie yeah sorry for the misleading first comment. I misinterpreted some commits to think @caarlos0 is also a core member. Thank you all of you guys for your efforts. (= Appreciate it. |
I've just started using this exporter, and would love to see some movement on this project. Personally, I'd love to see more people getting involved, and see it moving forward a bit. |
This is one of the awesome exporters which still works and I am also using it.It would be nice if either it can be transferred to prometheus-community or the PR's can be reviewed for merging.Thanks @zwopir for all the hard work. |
fwiw, me and @sysadmind are working on this fork: https://github.com/caarlos0/elasticsearch_exporter |
@caarlos0 FYI: We are currently in the process of moving this to prometheus-community :) |
Oh, nice, let me know if I can help 🙏 |
While I can align with our CI etc we will need maintainers :)
Le ven. 28 mai 2021 à 19:24, Carlos Alexandro Becker <
***@***.***> a écrit :
… Oh, nice, let me know if I can help 🙏
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#349 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACHHJVFQTCIRWECCMYGSDDTP7GTBANCNFSM4NJQVZ5Q>
.
|
The project was now moved to the prometheus-community org. All help welcome! |
Thank you for your work (= |
Is it still maintained? As I can see any contributions or comments from the core members @caarlos0 and @zwopir since the beginning of the year.
The text was updated successfully, but these errors were encountered: