chore: update server instrumentation to not reflect 400 status as error #1076
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ericmustin
requested review from
ahayworth,
arielvalentin,
dazuma,
fbogsany,
mwear and
robertlaurin
as code owners
fbogsany
approved these changes
Jan 6, 2022
|
@ericmustin thank you very much for this change. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
The specification as of late October/early November 2021 has been updated for http server spans so that 400 level responses should not create a span.status of
Errorbut instead should leave span status unset. Two instrumentations, rack and sinatra, were off spec and need to be updated, this PR updates them.see: