Moving this exporter to pometheus-community repo and maintainance flows?
frittentheke opened this issue · comments
Hey @Lusitaniae . First of all thank you very much for writing and maintaining this exporter!
Also for accepting suggestions and PRs!
May I bluntly bring up the idea to consider contributing this exporter to the promtheus-community? Apache is not some special and seldomly used special piece of software, but runs literally everywhere. As such having your exporter as part of the standard library of exporters (like e.g. there is for PostgreSQL https://github.com/prometheus-community/postgres_exporter) would be great and would allow others to assist with the maintenance work a little more.
Full disclosure: I am not affiliated with Prometheus in any way and did not ask e.g. @SuperQ or anybody prior to bringing this up here.
I simply suggested the same idea a while back for https://github.com/prometheus-community/smartctl_exporter as I believe it's really helpful to the ecosystem when there is more than "just" the curated list of exporters (https://prometheus.io/docs/instrumenting/exporters/), but a whole set of actively and community maintained exporters.
That's definitely an option, the core prometheus would definitely be better at maintaining this project than myself.
Not sure if they're interested to taking the project over and what would we need to do to make that happen
Thanks @Lusitaniae for being so open to this idea. I went ahead and opened issue prometheus-community/community#47 to ask @SuperQ @roidelapluie and others from Prometheus think.