PayloadRegexDecoder won't put anything in the message unless you add the message_fields subsection to tell it how to map the regex captures to the message fields.
That's moot, though, because you don't need a decoder. If you don't specify a decoder then each log line will just get dropped into the message payload. -r On 03/19/2015 01:04 PM, Ali wrote:
On Sat, Jan 31, 2015 at 9:45 AM Halid Rian <[email protected] <mailto:[email protected]>> wrote: Hi guys i would like to understand something about the DockerLogInput. So in the description it says it will gather all the logs from the running containers. That's the behaviour I'm expecting but my containers are running all kind of services so how does heka know which decoder to use? I'm getting started with Heka and DockerLogInput and am just trying to test my config to see what it's getting back from docker.sock. I don't yet know how decoders are written or how they work exactly. :-) Is there a general purpose decoder I can just plug in to see what's coming back from DockerLogInput? I modified the sanity_check.toml in the quickstart guide and added this: [DockerLogInput] endpoint = "unix:///var/run/docker.sock" But, predictably, I'm not seeing anything in the terminal when I interact with the docker daemon. I tried this, but it's not working either: [docker_decoder] type = "PayloadRegexDecoder" match_regex = '^(?P<Message>.*)$' [DockerLogInput] ... decoder = "docker_decoder" Thanks in advance, Ali _______________________________________________ Heka mailing list [email protected] https://mail.mozilla.org/listinfo/heka
_______________________________________________ Heka mailing list [email protected] https://mail.mozilla.org/listinfo/heka
