aws / aws/containers-roadmap

[EKS-Fargate] [request]: Allow customers to configure INPUT section of fluentBit configmap

Open
#1,720 0 comments 7 reactions 0 assignees View on GitHub
EKS Fargate FluentBit Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
Allow customers to configure INPUT section of fluentBit configmap, Currently INPUT is not supported but customers need to adjust values

**Which service(s) is this request for?**
This could be Fargate, EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
If customer wants to configure values like Skip_Long_Lines, Mem_Buf_Limit there's no way.

[INPUT]
Name tail
Tag kubernetes.*
Exclude_Path /var/log/containers/fluent*.log
Path /var/log/containers/*.log
Parser docker
DB /var/log/flb_kube.db
Mem_Buf_Limit 10MB
Skip_Long_Lines On
Refresh_Interval 10
Buffer_Chunk_Size 1MB
Buffer_Max_Size 1MB

**Are you currently working around this issue?**
Moving back to EC2 is the only option at this moment. Input section is completely ignored.

**Additional context**
https://docs.aws.amazon.com/eks/latest/userguide/fargate-logging.html

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

Contributor guide

Open the contributing guide

Research direction

Read the linked EKS Fargate logging documentation and compare its ConfigMap behavior with the requested Fluent Bit [INPUT] settings, including Mem_Buf_Limit and Skip_Long_Lines. Done means customers can configure the INPUT section instead of having it ignored, with the documented settings applied to Fargate logging.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
cloud, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.