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
We are experiencing data loss when writing our events to S3 using the below configuration. We do see everything in STDOUT, and to the FILE, but not in S3. We do not really know what is wrong, and it would be very helpful if someone could point out what might be wrong here. Or is this a bug?
This is using and EC2 with the Amazon version of td-agent: td-agent-3.6.0-0.amazon2.x86_64. The S3 is in the same region (us-east-1), so I do not believe this is a connection or bandwidth issue. We can send 100 concurrent requests and everything lads in S3, but if we go to 200, the S3 one does not have everything.
This issue has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days
We are experiencing data loss when writing our events to S3 using the below configuration. We do see everything in STDOUT, and to the FILE, but not in S3. We do not really know what is wrong, and it would be very helpful if someone could point out what might be wrong here. Or is this a bug?
This is using and EC2 with the Amazon version of td-agent: td-agent-3.6.0-0.amazon2.x86_64. The S3 is in the same region (us-east-1), so I do not believe this is a connection or bandwidth issue. We can send 100 concurrent requests and everything lads in S3, but if we go to 200, the S3 one does not have everything.
<match nTitleMe*.*>
@type copy
@type file
path /ntm/logs
compress gzip
timekey 1m
timekey_use_utc true
timekey_wait 1m
@type s3
The text was updated successfully, but these errors were encountered: