Hi, One way to do this right now is to use the MultiDecoder with cascade_strategy = "first-wins". I guess it will work ok, as long as you don't have a lot of different log types.
I believe that the best solution to this use-case would be to make the Source struct in DockerLogInput configurable ( https://github.com/mozilla-services/heka/blob/d115de2261f493a80e136cce717a936ee5063d63/plugins/docker/attacher.go#L185) and then declare multiple DockerLogInputs. Something like this: [DockerLogInput] container_name = "redis" decoder = "redis_decoder" [DockerLogInput] container_name = "apache" decoder = "apache_decoder" A third option would be to write your own decoder in Lua and then call other decoders based on value of the ContainerName-field. I'm not sure if your allowed to call other decoders from a sandbox though... // Anton 2015-01-31 16:45 GMT+01:00 Halid Rian <[email protected]>: > 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? > > _______________________________________________ > Heka mailing list > [email protected] > https://mail.mozilla.org/listinfo/heka > >
_______________________________________________ Heka mailing list [email protected] https://mail.mozilla.org/listinfo/heka
