Thanks for your interest in Heka. The current (v0.5) TcpOutput has disk queuing and should be able to support those needs. Note: the connection retry does have a timed back-off so it may not retry immediately when a new connection is established (the delay could be up to 10 seconds).
Thanks, Trink ----- Original Message ----- > From: "bruno binet" <[email protected]> > To: [email protected] > Sent: Tuesday, March 25, 2014 3:41:30 AM > Subject: [heka] heka with intermittent connection > Hi, > We are currently evaluating Heka which sounds promising for handling our logs > and metrics gathering and routing. > If possible, we also target to use Heka on low power sensors servers which > produces various metrics but have intermittent internet connection. > These low power devices typically run on an ARM/Linux board (like a Raspberry > PI) but would not be continuously connected to the Internet. They would have > some type of modem - satellite, GSM, 3G, etc - that would either dial up an > ISP occasionally to send all the data or use a permanent internet connection > which is subject to regular failures. > So I was wondering if Heka would support (already supports or is planed to > support) queuing up messages destined for an output (TCP) listener, > eventually buffering messages to disk, then send them as soon as the > connection is established again. > Or do you know if some opensource "bridging" solutions (that could > queue/buffer messages and send when online) already exist that I could > create an Heka output plugin for? > Or if developing this kind of feature in Heka core sounds valuable to you, > I'd appreciate any guidance to help me get it right. > Thanks, > Bruno > _______________________________________________ > Heka mailing list > [email protected] > https://mail.mozilla.org/listinfo/heka
_______________________________________________ Heka mailing list [email protected] https://mail.mozilla.org/listinfo/heka
