Yes to what Robbie said. Also, for debugging, you can set up a FileOutput or a LogOutput w/ `message_matcher = "TRUE"` and `encoder = "RstEncoder"`, which will show you the entire contents of every message that hits the router, written either to a file or to stdout.
-r On 02/02/2016 11:19 AM, Robbie Jacka wrote:
To match those inject messages, you'd need the following message matchers (respectively, line-by-line): message_matcher = "Payload == 'event' && Type == 'event' && Severity == 1" message_matcher = "Payload == 'event' && Type == 'event' && Severity == 1" message_matcher = "Type == 'event'" message_matcher = "Payload == 'event'" Also, since you don't specify a hekad instance for heka-inject, you'll need a local hekad instance running with a TcpInput using ProtobufDecoder. -- Robison Jacka / OpsEng / Weebly On Tue, Feb 2, 2016 at 10:52 AM, Scot <[email protected] <mailto:[email protected]>> wrote: Hi, New user to Heka, I am trying to test a new HttpOutput. On Openstack Kilo and LMA .7 and heka .9 I have tried all sorts of options but get nothing but silence. /usr/bin/heka-inject -payload="event" -type="event" -severity="1" /usr/bin/heka-inject -payload="event" -type="event" -severity="1" /usr/bin/heka-inject -type="event" /usr/bin/heka-inject -payload="event" root@fail# message_matcher = "Fields[payload_type] == 'json' && Fields[payload_name] == 'event'" _______________________________________________ Heka mailing list [email protected] <mailto:[email protected]> https://mail.mozilla.org/listinfo/heka _______________________________________________ Heka mailing list [email protected] https://mail.mozilla.org/listinfo/heka
_______________________________________________ Heka mailing list [email protected] https://mail.mozilla.org/listinfo/heka
