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
On 05/10/2016 12:37 PM, Tony Cesaro 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
You're trying to use a PayloadEncoder but you haven't specified that one is
available. ProtobufEncoder and ProtobufDecoder are the only ones that are
automatically declared. Try adding
[PayloadEncoder]
to your config.
-r
On 05/09/2016 06:56 AM, Roshan Radhakrishnan (roradhak) wrote:
Hi
I
Right, Heka currently has many more data ingestion plugins, so it's very useful
running on the endpoints snarfing up logs and system data and etc. One
possibility that interests me is extracting the Logstreamer code out of Heka
into a standalone utility, which could be used to feed data into
4 matches
Mail list logo
