Malcolm Rebughini

@rbagd thanks for trying it out. Can you provide more details on what you mean that the context doesn't get propagated in `task_postrun`? If there's an issue I have not...

@xrmx done with the rebase and added the changelog entry to unreleased :ok_hand:

I'm running into the same issue. @frankreno the fluentd plugin has now been deprecated. Is there any workaround on this? Cannot use https://github.com/SumoLogic/sumologic-kubernetes-collection

@frankreno it is an existing fluentd configuration and I would prefer to keep changes on the cluster to a minimum.

Here's the config: ``` log_level debug @type tail @label @containers path /var/log/containers/*.log exclude_path ["/var/log/containers/cloudwatch-agent*", "/var/log/containers/fluentd*", "/var/log/containers/kube*", "/var/log/containers/monitoring*", "/var/log/containers/calico*", ] pos_file /var/log/td-agent/fluentd-docker.pos tag core.* read_from_head false @type json time_format %Y-%m-%dT%H:%M:%S.%NZ @type...

I've found the code change that cause this. In [1.4.0](https://github.com/SumoLogic/fluentd-output-sumologic/blob/1.4.0/lib/fluent/plugin/out_sumologic.rb#L204) there was a function called expand_param that looked for record. this was replaced in 1.4.1 with `extract_placeholders`. Not very familiar...

After digging a bit, in newer versions of the fluentd api the proper way of doing this is adding a buffer and then referencing the chunk_key as `$.path.to.something`: ``` @type...