Date: Sat, 28 Apr 2018 22:24:00 -0700 From: Eitan Adler <lists@eitanadler.com> To: FreeBSD Hackers <freebsd-hackers@freebsd.org>, Ed Schouten <ed@nuxi.nl>, daniel.nelson@influxdb.com Subject: "Sysctl as a Service" for influxdb / telegraf Message-ID: <CAF6rxgkuOqWPXk%2BEEbsYqexktPH1BrQ9OY2WsQDM2vxndAfiRQ@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Resurrecting a somewhat old thread: I've been talking with the maintainer of telegraf about implementing an importer for the Prometheus exporter. They mentioned that they'd prefer a slightly different format. I'd like to add a new independent application similar to prometheus_sysctl_exporter for the influx wire format. Why independent? The set of options that each offer differ and the two formats will grow more different over time. For example prometheus supports descriptions, while influx support data types. Is there any objections to adding another application? If so, would a new output format for the existing binary be okay? References: Upstream issue: https://github.com/influxdata/telegraf/issues/4060 Proof of Concept: C code: https://ptpb.pw/At9H/c. I'm likely to factor out the common functions and include them as a single file when I commit. Original thread: https://lists.freebsd.org/pipermail/freebsd-hackers/2016-December/050283.html Wire format: https://docs.influxdata.com/influxdb/v1.5/write_protocols/line_protocol_tutorial/ -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxgkuOqWPXk%2BEEbsYqexktPH1BrQ9OY2WsQDM2vxndAfiRQ>