On 2016-01-14 14:59, Ramin Ali Dousti wrote:
Hi,
What is the best way of monitoring the proper working of a heka
instance? Let me give a concrete example: I have heka-1 that has log
files as input and TCP outputs to another heka instance. The second
one would receive the stream from the first one and publishes to
elastic search as well as influxdb. The simplest monitoring is the
process monitoring, making sure hekad is up, but what can be done
(what is the correct way) to make sure that heka-1 can send to heka-2
and heka-2 is able to publish to elastic search and influxdb?
As always any insight is greatly appreciated.
Interesting. Today I investigated a hekad that didn't want to start up.
I found out it was a large postgresql logline that was larger than the
sandbox' default output_limit. Processing the line ended up doubling
that. An increase to 128k sufficed.
This error raised several questions:
should a logline that is too big for my sandbox stop heka?
should our developers write better postgres queries (yes!), and
should I be monitoring heka to keep running?
Back on your subject:
1) http://hekad.readthedocs.org/en/v0.10.0/monitoring/index.html
2) I presume you can configure a "nagios output" inside heka
periodically emitting an "OK", but I lack an example. If you come up
with one, be sure to share it.
Regards,
Kai Storbeck
_______________________________________________
Heka mailing list
[email protected]
https://mail.mozilla.org/listinfo/heka
