Skip to content

Don't error on 3xx responses#4851

Draft
alex-pinkney-trp wants to merge 2 commits into
open-telemetry:mainfrom
troweprice:dont-error-on-3xx-responses
Draft

Don't error on 3xx responses#4851
alex-pinkney-trp wants to merge 2 commits into
open-telemetry:mainfrom
troweprice:dont-error-on-3xx-responses

Conversation

@alex-pinkney-trp

Copy link
Copy Markdown

Description

When making conditional requests to S3 get_object (e.g. using the IfNoneMatch or IfModifiedSince parameters) a 304 Not Modified response is returned wrapped in a ClientError exception. This causes S3.GetObject traces to be spuriously marked as error.

Fixes #4633

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

  • Added unit test coverage
    • tox -f test-instrumentation-botocore
  • uvx tox -e lint-instrumentation-botocore
  • uvx ruff check instrumentation/opentelemetry-instrumentation-botocore/

Does This PR Require a Core Repo Change?

  • No.

Checklist:

See contributing.md for styleguide, changelog guidelines, and more.

  • Followed the style guidelines of this project
  • Changelogs have been updated
  • Unit tests have been added
  • Documentation has been updated

@linux-foundation-easycla

Copy link
Copy Markdown

CLA Not Signed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Botocore instrumentation incorrectly marks S3 304 Not Modified as span error

1 participant