[Q&A] ECS agent logs marked as unreadable by Fluentd #4700
Unanswered
JuliannaBrandao
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What is a problem?
ECS Agent tail logging not working anymore after changing the image to Amazon Linux 2023. The configuration is the same as before.
The logs only show
<file.log> unreadable. It is excluded and would be examined next time.
, no more errors or warnings even when changing the fluentd logging to trace, so it doesn't look like the issue is rotation.The first source does work as expected, the second one is the one not working, so I know Kinesis is properly configured.
What I have done and did not work:
I wonder if my issue is related to this request: #4361
Original LS (before fix attempts):
Describe the configuration of Fluentd
`
@type tail
path /var/log/containers/*
pos_file /tmp/containers.log.pos
read_from_head true
tag docker
from_encoding UTF-8
encoding UTF-8
format multiline
format_firstline /\d{4}-\d{2}-\d{2}T/
format1 /^(?\d{4}-\d{2}-\d{2}T.*)/
refresh_interval 60s
multiline_flush_interval 3s
<match **>
log_level error `@type kinesis_streams_aggregated
compression zlib
stream_name <stream_name>
region eu-west-1
flush_interval 1
flush_thread_interval 0.1
flush_thread_burst_interval 0.01
flush_thread_count 15
chunk_limit_size 1m
buffer_type file
buffer_path /tmp/td-agent/buffer/log
flush_at_shutdown true
retry_max_times 15
retry_max_interval 5s
Describe the logs of Fluentd
Environment
Beta Was this translation helpful? Give feedback.
All reactions