Set pattern-specific tag

[pkaeding]

Is it possible to set a pattern-specific tag? I'd like to tag based on which pattern matched the message. The examples in the README show the tag being set at the top level, so maybe this can't be done, but it sure would be useful for what I'm trying to do.

[acrylicx]

+1 for this.
My current workaround for this is to use the @type copy to send it to multiple greps which then add suffix's based on which ones match. This however is an ugly workaround and means every message must be checked multiple times using regex.

[repeatedly]

Sorry, I missed this issue.
I will consider it.

[repeatedly]

This is impossible for now because parser plugin can't touch input plugin behaviour.
tag is configured in input plugin and parser plugin can't know it.

Hmm... one possible similar way is adding tag to records for rewrite-tag-filter.

[saurabtanej]

is there any update on this? We have multiple docker containers running having different pattern, is there a way we can filter the events based on pattern and tag them? @repeatedly

[rodrigodiez]

Same use case here, we use fluentd in a docker setup. We have up to 3 different formats coming from the same container: apache access, apache error and monolog.

We'd like to identify them and tag them separately. The final goal is to export to Elastic Search with a different _type field