-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Replicate /sampling endpoint from agent in the collector #1971
Comments
When this is done, update FAQ docs, cf. jaegertracing/documentation#335 |
Hi |
It's yours. |
Hi @namratachaudhary I have already submitted a PR for this issue. |
Open question: can clients be configured with a different sampling URL? |
Clients support the following config options:
Possible solutions:
Q: is it better to hardcode the final segments of the URL in the clients or make them configurable? Strictly speaking the URL path is part of the contract, e.g. if we introduce a different format of the sampling output it should become |
I would lean towards the consistency and require configuring the full URL. It's more flexible and one could deploy it on different path. |
@pavolloffay so you'd vote for JAEGER_SAMPLING_ENDPOINT? |
… as per jaegertracing/jaeger#1971 (comment) Signed-off-by: CI-Bot for Emmanuel Courreges <[email protected]>
…T environment variable (#200) * fix configuration from environment variables fix conversion to double of JAEGER_SAMPLER_PARAM rename env var JAEGER_SAMPLER_MANAGER_HOST_PORT to JAEGER_SAMPLER_SERVER_URL properly load JAEGER_SAMPLER_SERVER_URL Signed-off-by: CI-Bot for Emmanuel Courreges <[email protected]> * proper unit testing of RemotelyControlledSampler Signed-off-by: CI-Bot for Emmanuel Courreges <[email protected]> * include /sampling in all samplingServerURL examples to avoid confusion / or /whatever does not work for this driver: the agent answers slightly differently with a numerical strategyType Signed-off-by: CI-Bot for Emmanuel Courreges <[email protected]> * rename JAEGER_SAMPLER_MANAGER_HOST_PORT into JAEGER_SAMPLING_ENDPOINT as per jaegertracing/jaeger#1971 (comment) Signed-off-by: CI-Bot for Emmanuel Courreges <[email protected]>
This is done. |
Requirement - what kind of business use case are you trying to solve?
When using HTTP reporters in the clients to export tracing data directly to the collectors, users still want to be able to use remote sampler that loads centrally managed sampling strategies.
Problem - what in Jaeger blocks you from solving the requirement?
The
/sampling
endpoint is only implemented in the agent today.Proposal - what do you suggest to solve the problem or improve the existing situation?
Expose the same endpoint from the collectors, e.g.
/api/sampling
.The text was updated successfully, but these errors were encountered: