Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-26174

Add Uber-Trace-Id header to http proxy CONNECT request

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: HttpRepo
    • Labels:
      None
    • Location:
      External

      Description

      Artifactory is excelling in traceability, it is very consistent with it's inclusion of trace id in both logs and HTTP request as a header.

      A overlooked aspect for this traceability seem to be forwarding proxies.
      And improvement would be to include the Uber-Trace-Id header in the original HTTP CONNECT request made to proxy servers.

      Having this included would make system administrators able to associate individual request from Artifactory to the proxy logged in the proxy's access log (given the right config also log the header) with other JFrog logs even when working with for example HTTPS traffic.

      How this currently works.
      When making HTTP request to remote resources, Artifactory in most cases add header Uber-Trace-Id to the main outgoing request. When creating a TCP tunnel to a proxy with HTTP CONNECT the trace id is not included as a header in the CONNECT request and such can not be logged on the proxy.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            kimsondrup Kim Sondrup
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Sync Status

                Connection: RTFACT Sync
                RTMID-26175 -
                SYNCHRONIZED
                • Last Sync Date: