You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using this plugin in a fluentd forwarder/aggregator structure, where a fluentd forwarder runs as a DaemonSet on all nodes, forwarding all logs to fluentd aggregator pods running in a deployment. All filtering (including the kubernetes-metadata filter) is done on the aggregator.
When placing this plugin directly after the in_forward input plugin, only the first event in each event stream ("batch") is processed and continues to the next filter in the chain. All other logs get thrown away.
After further investigation, it seems that the call to first on this line causes problems when called on an instance of MessagePackEventStream, like the one returned from the in_forward plugin. When first is called before each on this instance, each returns only the first item.
Opened fluent/fluentd#2099 in fluentd regarding the weird behaviour of MessagePackEventStream.
The text was updated successfully, but these errors were encountered:
I'm using this plugin in a fluentd forwarder/aggregator structure, where a fluentd forwarder runs as a DaemonSet on all nodes, forwarding all logs to fluentd aggregator pods running in a deployment. All filtering (including the kubernetes-metadata filter) is done on the aggregator.
When placing this plugin directly after the in_forward input plugin, only the first event in each event stream ("batch") is processed and continues to the next filter in the chain. All other logs get thrown away.
After further investigation, it seems that the call to
first
on this line causes problems when called on an instance ofMessagePackEventStream
, like the one returned from the in_forward plugin. Whenfirst
is called beforeeach
on this instance,each
returns only the first item.Opened fluent/fluentd#2099 in fluentd regarding the weird behaviour of
MessagePackEventStream
.The text was updated successfully, but these errors were encountered: