diff --git a/docs/patterns/images/logs-fargate-fluentbit.png b/docs/patterns/images/logs-fargate-fluentbit.png new file mode 100644 index 00000000..0741eda8 Binary files /dev/null and b/docs/patterns/images/logs-fargate-fluentbit.png differ diff --git a/docs/patterns/single-new-eks-observability-accelerators/single-new-eks-fargate-opensource-observability.md b/docs/patterns/single-new-eks-observability-accelerators/single-new-eks-fargate-opensource-observability.md index 08004375..fe7e0071 100644 --- a/docs/patterns/single-new-eks-observability-accelerators/single-new-eks-fargate-opensource-observability.md +++ b/docs/patterns/single-new-eks-observability-accelerators/single-new-eks-fargate-opensource-observability.md @@ -194,8 +194,10 @@ You should now see a new dashboard named `Java/JMX`, under `Observability Accele ## Viewing Logs -By default, we deploy a FluentBit daemon set in the cluster to collect worker logs for all namespaces. Logs are collected and exported to Amazon CloudWatch Logs, which enables you to centralize the logs from all of your systems, applications, -and AWS services that you use, in a single, highly scalable service. +Amazon EKS on Fargate offers a built-in log router based on Fluent Bit. This means that you don't explicitly run a Fluent Bit container as a sidecar, but Amazon runs it for you. All that you have to do is configure the log router. The configuration happens through a dedicated [`ConfigMap`](../../../lib/common/resources/fluent-bit/fluent-bit-fargate-config.ytpl). Logs are collected and exported to Amazon CloudWatch Logs, which enables you to centralize the logs from all of your systems, applications, +and AWS services that you use, in a single, highly scalable service. By default, the logs are exported to us-east-1 region but you can modify the `ConfigMap` for your region of choice. At least one supported `OUTPUT` plugin has to be provided in the `ConfigMap` to enable logging. You can also modify the destination from cloudwatch to Cloudwatch (default), Amazon OpenSearch Service or Kinesis Data Firehose. Read more about [EKS Fargate logging](https://docs.aws.amazon.com/eks/latest/userguide/fargate-logging.html). + +![fargate-fluentbit](../images/logs-fargate-fluentbit.png) ## Teardown diff --git a/lib/common/resources/fluent-bit/fluent-bit-fargate-config.ytpl b/lib/common/resources/fluent-bit/fluent-bit-fargate-config.ytpl new file mode 100644 index 00000000..53871b4d --- /dev/null +++ b/lib/common/resources/fluent-bit/fluent-bit-fargate-config.ytpl @@ -0,0 +1,42 @@ +kind: Namespace +apiVersion: v1 +metadata: + name: aws-observability + labels: + aws-observability: enabled +--- +kind: ConfigMap +apiVersion: v1 +metadata: + name: aws-logging + namespace: aws-observability +data: + flb_log_cw: "{{enableFlbProcessLogs}}" # Set to true to ship Fluent Bit process logs to CloudWatch. + filters.conf: | + [FILTER] + Name parser + Match * + Key_name log + Parser crio + [FILTER] + Name kubernetes + Match kube.* + Merge_Log On + Keep_Log Off + Buffer_Size 0 + Kube_Meta_Cache_TTL 300s + output.conf: | + [OUTPUT] + Name cloudwatch_logs + Match kube.* + region {{awsRegion}} + log_group_name {{logGroupName}} + log_stream_prefix {{log_stream_prefix}} + auto_create_group true + parsers.conf: | + [PARSER] + Name crio + Format Regex + Regex ^(?