You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This deploys fine but all the older logGroups still have never as retention period .
Below is the fluent-bit.conf.
[SERVICE]
HTTP_Server On
HTTP_Listen 0.0.0.0
HTTP_PORT 2020
Health_Check On
HC_Errors_Count 5
HC_Retry_Failure_Count 5
HC_Period 5
Parsers_File /fluent-bit/parsers/parsers.conf
[INPUT]
Name tail
Tag kube.*
Path /var/log/containers/*.log
DB /var/log/flb_kube.db
Parser docker
Docker_Mode On
Mem_Buf_Limit 5MB
Skip_Long_Lines On
Refresh_Interval 10
[FILTER]
Name kubernetes
Match kube.*
Kube_URL https://kubernetes.default.svc.cluster.local:443
Merge_Log On
Merge_Log_Key data
Keep_Log On
K8S-Logging.Parser On
K8S-Logging.Exclude On
Buffer_Size 32k
[OUTPUT]
Name cloudwatch_logs
Match *
region us-west-2
log_group_name /aws/eks/fluentbit-cloudwatch/logs
log_group_template /aws/eks/fluentbit-cloudwatch/workload/$kubernetes['namespace_name']
log_stream_prefix fluentbit-
log_stream_template $kubernetes['pod_name'].$kubernetes['container_name']
auto_create_group true
log_retention_days 90
The policy attached to this role has required permissions as well
shubhindia
changed the title
[aws-for-fluent-bit] logRetentionPeriod is not working
[aws-for-fluent-bit] logRetentionPeriod parameter is not working
Nov 29, 2023
shubhindia
changed the title
[aws-for-fluent-bit] logRetentionPeriod parameter is not working
[aws-for-fluent-bit] logRetentionPeriod parameter is not working for existing logGroups
Nov 29, 2023
I deployed a FluentBit setting the retention to 14 days, but When I change the same parameter to 7 days. The fluentBit doesn't update the retention policy in CW LogGroups existing
I have deployed aws-for-fluent-bit with logRetention set to 90 days using argo.
Below is the argo application yaml
This deploys fine but all the older logGroups still have
never
as retention period .Below is the fluent-bit.conf.
The policy attached to this role has required permissions as well
The text was updated successfully, but these errors were encountered: