Masahiro Nakagawa

> Once all is started, I monitor udp traffic and I can see udp packet losses every second. Does it mean netflow input plugin receives broken packet?

@nargmarg If you have a problem, need to write configuration and actual log example. We are not psychic, so hard to reply the answer without the information :)

> I know you can use time_format in multi_format Yes. This plugin forwards configurations and events to actual parser plugins, so parser features should be worked. I tested with simple...

Could you send this patch to fluent-plugin-kafka's README? fluentd-docs-gitbook's article uses short-description because hard to sync plugin update. Update fluent-plugin-kafka README and link to it is better.

> @id in the section. `@id` should be in output configuration, not ``. Could you re-check your configuration? Example from docs: ``` workers 2 root_dir /var/log/fluentd @type forward @id out_fwd...

Current log message is misleading. Send a patch: https://github.com/fluent/fluentd/pull/2751

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

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...

`record_modifier` mutates incoming records in-place, so this behavior is expected. You need to change process order in `out_copy`. ``` @type copy @type relabel @label @EVENTLOG.LOGICMONITOR @type relabel @label @EVENTLOG.SCALYR ```

Currently, no way. Writing such routine in `${...}` is one way like this: https://groups.google.com/d/msg/fluentd/uh0Vb_sOFz4/WSZRHGXcAgAJ