One option would be to use MQTT as the transport. It fits really well with metrics use case but I don't think the collectd-mqtt writer was ever finished....
2015-06-11 22:24 GMT+02:00 Konstantin Tokarev <annu...@yandex.ru>: > > > 11.06.2015, 21:56, "Florian Forster" <o...@collectd.org>: > > Hi Konstantin, > > > > On Thu, Jun 11, 2015 at 03:08:04PM +0300, Konstantin Tokarev wrote: > >> Is it a design desition that network plugin supports UDP and > >> multicast, but not TCP? > > > > yes, it allowed us to implement support for multicast, which is not > > possible with TCP. > > What's wrong with just sending the same packets over TCP connection? > > > > >> I think using TCP would be better option than UDP for transmitting > >> data over Internet. Otherwise, collectd would need to mitigate UDP > >> packet loss somehow. > > > > You can work around this with the AMQP plugin, for example. I'd also > > like to have a reliable-by-default option, but the idea I have in mind > > is not quite there yet … > > I'm planning to use collectd on embedded systems, and AMQP requires > additional dependency. Also, it's not a binary protocol. > > -- > Regards, > Konstantin > > _______________________________________________ > collectd mailing list > collectd@verplant.org > http://mailman.verplant.org/listinfo/collectd >
_______________________________________________ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd