Awesome, thanks for the insight, Florian!

I suggest to mark the collectd_exporter then, and move it into our junkyard
organization after a while of nobody complaining. I'll send a PR for that.

On Sun, May 10, 2020 at 9:36 PM Florian Forster <f...@octo.it> wrote:

> Hi Julius, hi Harald, hi lists,
>
> I'm not aware of anything that the collectd_exporter does that the
> "write_prometheus" plugin doesn't support – and I'm happy to get the
> plugin to feature parity if anything comes up.
>
> When switching to the plugin, a collectd_exporter that is running
> alongside collectd (like a sidecar or some such) can be removed. A
> collectd_exporter that is running centrally (many collectd's, one
> exporter) can be replaced by a collectd or Prometheus instance. Either
> way, the overall complexity of the setup is reduced. (*)
>
> Hope this helps :)
> Best regards,
> —octo
>
> (*) In theory. I'm not operating such a setup myself.
>
> On 2020-05-10 13:22, Julius Volz wrote:
> > That's a good question - googling I found
> > https://collectd.org/wiki/index.php/Plugin:Write_Prometheus, which
> > says:
> >
> > "This plugin is similar in scope to the collectd_exporter written by
> > the Prometheus team and uses the same naming schema so it can be used
> > as a drop-in alternative."
> >
> > So maybe we could indeed deprecate the Collectd Exporter. I'm just not
> > familiar enough with Collectd to say for sure if the exporter is doing
> > anything important over that plugin.
> >
> > +cc Florian Forster, who was involved in both - maybe you can provide
> > more insight?
> >
> > On Sat, May 9, 2020 at 5:59 PM Harald Koch <harald.k...@gmail.com>
> > wrote:
> >
> >> On Sat, May 9, 2020, at 04:23, Ben Kochie wrote:
> >>
> >> On Fri, May 8, 2020, 16:10 Julius Volz <julius.v...@gmail.com>
> >> wrote:
> >>
> >> By some historic accident I became the maintainer of the collectd
> >> exporter (https://github.com/prometheus/collectd_exporter), although
> >> I have never used collectd myself and know very little about it.
> >> This has led to some neglect from my side...
> >>
> >> Does anyone feel invested in collectd and feels qualified to
> >> maintain it?
> >
> > Collectd has a built-in prometheus exporter, so I don't know if this
> > is still necessary?
> >
> > --
> >
> > Harald
> >
> >  --
> > You received this message because you are subscribed to the Google
> > Groups "Prometheus Users" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> > an email to prometheus-users+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/prometheus-users/5f06967f-7ed0-4410-a60c-1df6175736ea%40www.fastmail.com
> > [1].
> >
> >
> > Links:
> > ------
> > [1]
> >
> https://groups.google.com/d/msgid/prometheus-users/5f06967f-7ed0-4410-a60c-1df6175736ea%40www.fastmail.com?utm_medium=email&amp;utm_source=footer
>
> --
> Florian octo Forster
> Hacker in training
> GnuPG: 0x0C705A15
> http://octo.it/
>
> --
> 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 prometheus-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/prometheus-developers/0308385b38dfe2e30e18f8f95bbe8af2%40octo.it
> .
>


-- 
Julius Volz
PromLabs - promlabs.com

-- 
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 prometheus-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-developers/CAObpH5xa3S%3DszC9UU337M4%2BDOatmxRmnvYkgrFYHcsNQYbHBYA%40mail.gmail.com.

Reply via email to