Wesley Pettit

> Fargate validates against the following supported filters: grep, parser, record_modifier, rewrite_tag, throttle, nest, modify, and kubernetes. https://docs.aws.amazon.com/eks/latest/userguide/fargate-logging.html

@iconara I like the idea that Fargate could be used like Lambda! For the specific problem you mentioned, I'd like to propose a workaround that you could use right now....

I am working on implementing this EDIT: Actually I am not sure how but somehow I was confused and thought this repo was related to the k8s ruby plugin for...

Change is here: https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter/pull/337 It is already released in the plugin version 2.11.1 Though I am still working on doing final testing actually... but as far as we can tell...

(It works don't worry)

@vgaddavcg Changes are merged here: https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter/pull/337 And released in plugin version 2.11.1 from what I saw. Anything else beyond that is up to you folks to handle

@scholzj @vgaddavcg Sorry yea it seems that I got confused and thought this repo was also related to Fluentd... apologies, I have not fixed anything in this repo.

> Although I'm afraid Amazon has shifted their development efforts to EKS.. @koenpunt We're still actively developing Amazon ECS and care deeply about it! [See our roadmap](https://github.com/aws/containers-roadmap/issues?q=is%3Aissue+is%3Aopen+label%3AECS) Blox however unfortunately...

@davidnewhall @pranavmarla I'm fine with the feature request... it'd be up the user to make sure they intelligently pick the fallback name... but I'm fine with that. > I think...

@Drupi > Hello! Is it possible to also enable this? https://docs.fluentbit.io/manual/administration/configuring-fluent-bit/record-accessor Unfortunately that feature is not available to go plugins. However, the log stream/group name templating feature that David built...