-
Notifications
You must be signed in to change notification settings - Fork 782
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
Start adding error annotation #384
Comments
here's some hints here openzipkin/openzipkin.github.io#52 main thing is that we shouldn't have a span dangling (ex only cr) as the span detail tab looks off. |
marcingrzejszczak
added a commit
that referenced
this issue
Oct 28, 2016
without this change there's no error colouring on Zipkin side with this change we set error tags - whenever there is an exception thrown on the server side (5xx) - wheneber on the client side it's impossible to send a message fixes #384
marcingrzejszczak
added a commit
that referenced
this issue
Oct 28, 2016
without this change there's no error colouring on Zipkin side with this change we set error tags - whenever there is an exception thrown on the server side (5xx) - wheneber on the client side it's impossible to send a message fixes #384
marcingrzejszczak
added a commit
that referenced
this issue
Oct 31, 2016
without this change there's no error colouring on Zipkin side with this change we set error tags - whenever there is an exception thrown on the server side (5xx) - wheneber on the client side it's impossible to send a message fixes #384
marcingrzejszczak
added a commit
that referenced
this issue
Oct 31, 2016
without this change there's no error colouring on Zipkin side with this change we set error tags - whenever there is an exception thrown on the server side (5xx) - wheneber on the client side it's impossible to send a message fixes #384
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With Zipkin 1.3 https://github.com/openzipkin/zipkin/releases/tag/1.3.0 and openzipkin/zipkin#1140
error
annotations can be resolved into a nice visualization in the UI.The text was updated successfully, but these errors were encountered: