Skip to content

aws_s3 SQS fetch errors should be reported as warnings #18855

Open
@jszwedko

Description

@jszwedko

A note for the community

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

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



{
--
 
error_code | failed_fetching_sqs_events
error_type | request_failed
level | ERROR
span{
 
component_id | cloudfunnel_bucket
component_kind | source
component_name | cloudfunnel_bucket
component_type | aws_s3
name | source
}
spans[
 
{
 
component_id | cloudfunnel_bucket
component_kind | source
component_name | cloudfunnel_bucket
component_type | aws_s3
name | source
}
]
stage | receiving
target | vector::internal_events::aws_sqs::s3
timestamp | 2023-10-15T18:26:42.199067Z
}


Example Data

No response

Additional Context

No response

References

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    source: aws_s3Anything `aws_s3` source relatedtype: bugA code related bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions