aws_s3
SQS fetch errors should be reported as warnings
#18855
Labels
aws_s3
SQS fetch errors should be reported as warnings
#18855
Uh oh!
There was an error while loading. Please reload this page.
A note for the community
Problem
Currently, if an SQS message fetch fails (e.g. due to a dropped connection) it is reported as an error when it should really be a warning given it will retry on the next poll interval.
Configuration
No response
Version
vector v0.23.0
Debug Output
Example Data
No response
Additional Context
No response
References
No response
The text was updated successfully, but these errors were encountered: