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
enhance tracing #887
enhance tracing #887
Conversation
feature: add hostname tag to ingress span to show the instance of the trace feature: trace log retries Signed-off-by: Sandor Szücs <sandor.szuecs@zalando.de>
fde3d4f
to
ef6ca53
Compare
if span := ot.SpanFromContext(ctx.Request().Context()); span != nil { | ||
span.LogKV(`circuit_breaker`, `open`) | ||
} | ||
tracing.LogKV("circuit_breaker", "open", ctx.request.Context()) |
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.
Here can add a error tag true which shows in the ui.
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.
We should also do that in case of any proxy errors.
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.
I added it to the ingress span in case proxy.do() returns an error, because the client does not care which part errors and the proxy span already sets this tag on error in proxy.makeBackendRequest
…l error returns from proxy.do() Signed-off-by: Sandor Szücs <sandor.szuecs@zalando.de>
👍 |
1 similar comment
👍 |
This PR partially solved #797, because it now logs start and stop in the trace and has one span open for all request filter processing. |
related: #860
feature: trace filters and log filter names start/stop
feature: add hostname tag to ingress span to show the instance of the trace
feature: trace log retries
Signed-off-by: Sandor Szücs sandor.szuecs@zalando.de