-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
New Feature - Add the traceid in the response headers #280
Comments
@zpf1989 That sounds fine to me but I would probably make it configurable. Some users might not want to expose the trace ID. Maybe extend this feature e.g.. "DownstreamHeaderTransform": {
"Trace-Id": "Trace-Id, {TraceId}"
}, This would then add the TraceId as a header called Trace-Id but Trace-Id could be whatever you want. I will look into it asap! |
Yeah,that's considerate! |
…te the header place holder stuff
released in version 5.1.0 |
Hi,we are using Butterfly in Ocelot for tracing.
Generally,when client request fails,we want to find the exact trace quickly.
I think it is fastest to search a trace by traceId ,because it matches only one trace.
So could you add the traceid in the response headers when using tracing before return?
Just like this below:
responseMessage.Headers.TryAddWithoutValidation("TraceId", span.SpanContext.TraceId);
Ocelot/src/Ocelot/Requester/OcelotHttpTracingHandler.cs
Line 58 in c1b3151
Thanks!
The text was updated successfully, but these errors were encountered: