-
Notifications
You must be signed in to change notification settings - Fork 264
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
correlation id in response header #177
Comments
Does https://github.com/zalando/tracer solve your problem? Using it a trace can span more than just a single request-response-pair. |
I've just tried, and this is what I understand:
so - that makes it a bit difficult to join:
the best option would be to have |
@lsntomaszw Sorry for the late response:
It also adds it to the request, if it's not already present. Therefore the following statement is incorrect:
In order to make this setup work you need to register the TracerFilter before the LogbookFilter.
That would be too invasive for logbook. The purpose of the library is to log traffic, not change it. Tracer is the best match for your use case. All you need to know is the trace id. Either the client got it back as a response or they already provided it themselves with the initial request. Either way, you'll have it. The following doc explains why we have correlation id in the first place: https://github.com/zalando/logbook/blob/master/docs/scalyr.md |
Is there any way to return correlation Id not just in log, but also in response? Having that value in response (header) will allow developers / testers to provide id of the request/response that should be tracked for bugs etc.
The text was updated successfully, but these errors were encountered: