[
https://issues.apache.org/jira/browse/KNOX-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482735#comment-17482735
]
ASF subversion and git services commented on KNOX-2704:
-------------------------------------------------------
Commit 4073660cc307fe3f769ddd3f521d15a3b50293ec in knox's branch
refs/heads/master from Sandeep Moré
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=4073660 ]
KNOX-2704 - Honor request id (correlation id) set by upstream loadbalancer
(#534)
* KNOX-2704 - Honor request id (correlation id) set by upstream loadbalancer
> Honor request id (correlation id) set by upstream loadbalancer
> --------------------------------------------------------------
>
> Key: KNOX-2704
> URL: https://issues.apache.org/jira/browse/KNOX-2704
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: Sandeep More
> Assignee: Sandeep More
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In case request Id/correlation id is set by upstream LB (e.g. nginix) (or
> other components) do not generate one and use the one passed.
> Request Id also known as trace id is passed as a "X-Request-Id" header
> value. This is a good blog post on how it can be used
> https://blog.heroku.com/http_request_id_s_improve_visibility_across_the_application_stack
> This would help Knox be in line with other components supporting trace id for
> better telemetry and tracing.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
