This repository has been archived by the owner on May 23, 2024. It is now read-only.
Provide ability for clients to add HTTP headers #479
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which problem is this PR solving?
Resolves: #478
When services, such as jaeger-collector, are deployed to production, they are assigned ephemeral IP addresses and ports when listening for HTTP requests.
In order for caller services (whether calling from development or production) to reach specific endpoints of callee services, a side-car process is used to route the outbound request to the correct IP and port which is achieved by providing the:
Currently, jaeger-client-go does not provide a capability for clients to flexibly add headers to the outbound HTTP request.
Short description of the changes
Headers
toReporterConfig
NewHTTPTransport