[
https://issues.apache.org/jira/browse/KNOX-2704?focusedWorklogId=715989&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-715989
]
ASF GitHub Bot logged work on KNOX-2704:
----------------------------------------
Author: ASF GitHub Bot
Created on: 26/Jan/22 20:39
Start Date: 26/Jan/22 20:39
Worklog Time Spent: 10m
Work Description: moresandeep merged pull request #534:
URL: https://github.com/apache/knox/pull/534
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@knox.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 715989)
Time Spent: 50m (was: 40m)
> 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: 50m
> 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)
