-
Notifications
You must be signed in to change notification settings - Fork 495
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mark the span as error when the HTTP transporter fails #950
Mark the span as error when the HTTP transporter fails #950
Conversation
Signed-off-by: Xabier Larrakoetxea <me@slok.dev>
Signed-off-by: Xabier Larrakoetxea <me@slok.dev>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! I ran into this yesterday when instrumenting a kubernetes webhook myself...
Codecov Report
@@ Coverage Diff @@
## main #950 +/- ##
=======================================
+ Coverage 75.4% 75.6% +0.1%
=======================================
Files 69 69
Lines 4458 4460 +2
=======================================
+ Hits 3363 3372 +9
+ Misses 952 946 -6
+ Partials 143 142 -1
|
Signed-off-by: Xabier Larrakoetxea <me@slok.dev>
This looks ready to merge outside of fixing the lint issues:
|
Signed-off-by: Xabier Larrakoetxea <me@slok.dev>
Done! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few minor comments to the test code. Nice 👍
…on some test parts Signed-off-by: Xabier Larrakoetxea <me@slok.dev>
Hi! 👋
Currently, the HTTP Transporter is recording the errors, however, is not marking the span as an error, and this is misleading. For example, if the Request fails because there is nobody listening to our client calls we would not see that the request has failed easily (unless an upper layer records the error):
Before:
After the fix: