Hiroshi Hatake

`enable_msgpack_time_support` in system directive may help you. ```aconf enable_msgpack_time_support true ``` ref: https://docs.fluentd.org/deployment/system-config#enable_msgpack_time_support This option makes to be able to handle Time object to encode msgpack object with Fluentd.

This is because fluent-plugin-rewrite-tag-filter is not contained this image. If you want to build your own image, please refer to the section: https://github.com/fluent/fluentd-docker-image#how-to-build-your-own-image

Hmm.., we need to consider additional things. This PR should not work.

I'd rechecked code but I don't notice any mistake. Cheetah plugin also uses this style procedure/member.

Hmm…, I see. Marking as deprecated is reasonable.

Using Golang plugin mechanism is quite reasonable. But, in this golang module ("github.com/fluent/fluent-bit-go/input"), we should keep it as very thin package. Providing another wrapper module is reasonable for me.

I mean, plugin authors can choose to import plugin bridge code something like `"github.com/fluent/fluent-bit-go/bridge/input"` but this PR shouldn't include patches for bridging code. We should do it in another PR....

Yeah, we noticed that but current fluent-bit is pointed for 2.0 development. If we will merge this PR, we have to create 2.0 branch for now.

Oh! You'd already send this into https://github.com/logstash-plugins/logstash-patterns-core/pull/284. We'll update grok patterns after https://github.com/logstash-plugins/logstash-patterns-core/pull/284 is merged in upstream.

This plugin does not work contaminated structured log. 1-by-1 formatted log can be handled like with (Note that this configuration is pseudo configuration not the real one): ```aconf @type tail...