> On May 10, 2016, at 12:37 PM, Tony Cesaro <aces...@gmail.com> wrote: > > One of the big selling features for me was the fact that we can deploy heka > as an agent or a server, with the same executable and configure it to assume > the role of one or the other (or both). Splitting these into separate > executables would be a negative in my opinion. > > Another point I wanted to clarify is whether heka is somehow "going away," > which I would assume isn't the case. We've never seen capacity issues with > heka itself (though we've never pushed it to extreme limits) and it's been > much less bug prone than Logstash, so we're going to keep using it for the > indefinite future. We may upgrade to 0.10 just to get some of the disk > buffering features, but with the Lua sandbox, there aren't any immediately > foreseeable problems on the monitoring infrastructure that I can see not > solving with it. > > To summarize my question, it's not being deleted from GitHub and Read the > Docs, is it?
_______________________________________________ Heka mailing list Heka@mozilla.org https://mail.mozilla.org/listinfo/heka
