On 01/07/2016 03:09 PM, Emily Gu wrote:
Thanks David for all the help! I'll give it a try.
Please bear with me as some parts I still not understand.
1. Why do I have to run two Heka instances where one for input and
another for output?
Because if you send the output from a Heka instance back into itself,
then you're likely setting up an infinite loop of traffic that will spin
out of control.
2. Did you mean I need to specify different share_dirs in input and
output Toml configs?
If you're running multiple Heka instances on a single machine, it
*should* be fine for them to use the same share_dir, which is read-only.
It's very important that each specifies a unique base_dir, however,
since that's used by Heka for internal bookkeeping data. Two Heka's
using the same base_dir is asking for trouble.
3. Do I need both TcpOutput and FileOutput in order for me to see
messages inside an output file? What if I didn't specify TcpOutput?
Um, TcpOutput sends output data over a TCP connection. It expects that
there is a listener on the other side which will accept that TCP
connection, and will know how to correctly handle the data that Heka is
sending over the TCP connection.
FileOutput sends data to a file on the local file system.
It's of course fine to specify a FileOutput without specifying a TcpOutput.
-r
_______________________________________________
Heka mailing list
[email protected]
https://mail.mozilla.org/listinfo/heka
