Amazon EKS on AWS Fargate now Supports the Fluent Bit Kubernetes Filter
Amazon Elastic Kubernetes Service (EKS) on Fargate now supports the use of Kubernetes Fluent Bit filters which provide enriched Kubernetes-specific metadata to Fluent Bit logs. Customers can now more easily observe and troubleshoot their applications by using the Kubernetes pod, container, or namespace name, among other Kubernetes metadata, to associate with their applications’ logs.
Amazon Elastic Kubernetes Service (EKS) on Fargate now supports the use of Kubernetes Fluent Bit filters which provide enriched Kubernetes-specific metadata to Fluent Bit logs. Customers can now more easily observe and troubleshoot their applications by using the Kubernetes pod, container, or namespace name, among other Kubernetes metadata, to associate with their applications’ logs.
Without support for the Kubernetes filter for Fluent Bit on EKS Fargate, customers had to manually read through log files to find the events they were interested in and it was difficult to associate a given log line with a Kubernetes application. Some customers who needed this kind of observability were unable to use Fargate with EKS and couldn’t benefit from its fully managed compute environment.
Today, customers can more easily find the information they need in their EKS clusters’ Fluent Bit logs using the Kubernetes metadata added by the Kubernetes filter. By creating a Kubernetes ConfigMap that includes the Fluent Bit Kubernetes filter configuration, the logs for your EKS Fargate cluster are designed to automatically be annotated with Kubernetes metadata.
To learn more, visit the Amazon EKS Fargate logging documentation. To learn more about Amazon EKS, visit our product page.