Wesley Pettit

@tri-bao @hou-yimin EKS has rolled back this launch, so we have re-opened this issue and moved it to "Coming Soon". Apologies for the inconvenience here!!

@tri-bao The EKS helm chart is different than the EKS Fargate built-in logging hidden container: https://docs.aws.amazon.com/eks/latest/userguide/fargate-logging.html The latest version of the helm chart supports multiline logging for all EKS EC2...

Once launched, this repo should be updated or archived: https://github.com/aws-samples/amazon-ecs-fluent-bit-daemon-service/issues/3

I suspect this will require changes in the shim loggers: https://github.com/aws/amazon-ecs-shim-loggers-for-containerd

I should note that my original examples are not complete, this is what real split logs should look like, note the multiple partial message fields: ``` {"source"=>"stdout", "log"=>"{"payload": "0123456789......01234567890abcdef", "partial_message"=>"true",...

@marksumm I can not provide an ETA or launch date, however, this hasn't been forgotten and I am working on it.

@marksumm implementation complete: https://github.com/aws/amazon-ecs-shim-loggers-for-containerd/pull/24

``` ``` 147dda285fd4:bottlerocket-eks wppttt$ kubectl -n amazon-cloudwatch logs fluent-bit-fbf8584f8-vvsnl Fluent Bit v1.9.10 * Copyright (C) 2015-2022 The Fluent Bit Authors * Fluent Bit is a CNCF sub-project under the umbrella...

## OperationAbortedException with log_group_class: Race Condition between Fluent Bit instances Below is normal even if the log_group_class was successfully set. ``` [2024/05/17 03:47:49] [ info] [output:cloudwatch_logs:cloudwatch_logs.0] Creating log group infrequent-access-test16/containerinsights/Bottlerocket-Linux-v1-29/application...

``` [OUTPUT] Name cloudwatch_logs Match dataplane.* region ${AWS_REGION} log_group_name standard-access-test16/containerinsights/${CLUSTER_NAME}/dataplane log_stream_prefix ${HOST_NAME}- auto_create_group true extra_user_agent container-insights log_group_class STANDARD ```