I would prefer to start with an offer to give someone else access to maintain the code, rather than shutdown an existing codebase.
If this fork is better, maybe we can get them to merge everything and they take over? Another option, we move it to prometheus-community. On Wed, Feb 26, 2020 at 5:00 PM Bjoern Rabenstein <[email protected]> wrote: > Hi Prometheans, > > If you are not interested at all in integrating Nagios with > Prometheus, you can stop reading now. > > Otherwise, you are probably aware of the little plugin I maintain in > the https://github.com/prometheus/nagios_plugins repository. (The > plural is a lie, I guess when the repo was created by Joshua Hoffman > back in 2013, we had bolder plans with the integration than just one > measly shell script.) > > Having an own repo in the prometheus GH org kind of suggests that > the Nagios integration is important and 1st class. Which is simply not > true. If we didn't have that repo today, we would certainly encourage > such an integrations to be maintained in a 3rd party repository, like > the hundreds of other integrations. The reason why the repo exists in > the prometheus GH org is purely historical (i.e. SoundCloud needed the > integration back then in 2013, and with essentially no other users > than SoundCloud itself, it was just natural to put it into the > prometheus GH org). > > On top of that, I am not using Nagios anymore. One of my > accomplishments at SoundCloud was to remove Nagios/Icinga from the > tech stack. And Grafana Labs, my current employer, doesn't use > Nagios/Icinga either. > > For the time being, I have been happy to keep maintaining the > prometheus/nagios_plugins repo, including reviewing the occasional bug > fix or minor improvement contributed to the project. However, > inevitably more involved feature requests or even contributions will > happen, and I don't feel qualified to review those. One of them can be > seen here: https://github.com/prometheus/nagios_plugins/issues/25 > (The discussion on that issue is what lead to this mail of mine.) > > I can see two options to go from here: > > 1. We find somebody that is qualified to maintain > prometheus/nagios_plugins in place. > > 2. We deprecate prometheus/nagios_plugins and refer to a 3rd party > integration (possibly based on forking prometheus/nagios_plugins) that > is properly maintained and developed. In this case, I'd keep the > existing repo around until further notice, but not accepting any > contributions besides important bug fixes. > > Emil 'Skeen' Madsen, @Skeen on GH, filed above mentioned issue #25, > and he is already playing around with a feature-enriched fork. I would > now like to encourage Nagios/Icinga users to try out his fork, to be > found under https://github.com/magenta-aps/check_prometheus_metric and > give Emil feedback. If that turns out well, I suggest to go for > option (2), deprecate prometheus/nagios_plugins in lieu of > agenta-aps/check_prometheus_metric and list the latter as an > integration on https://prometheus.io > > Please let me know what you think. > -- > Björn Rabenstein > [PGP-ID] 0x851C3DA17D748D03 > [email] [email protected] > > -- > You received this message because you are subscribed to the Google Groups > "Prometheus Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/prometheus-developers/20200226160040.GJ27526%40jahnn > . > -- You received this message because you are subscribed to the Google Groups "Prometheus Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-developers/CABbyFmrdYyk3X27EV9NpV5woZ30hODuzDX5ZzknA%2B3ngQZMNAQ%40mail.gmail.com.
