-
Notifications
You must be signed in to change notification settings - Fork 523
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
[Jaeger] Add gRPC Sampling endpoint #3487
Milestone
Comments
simitt
added a commit
to simitt/apm-server
that referenced
this issue
Mar 16, 2020
Support fetching Jaeger gRPC sampling strategy from APM server. Only probabilistic sampling is supported. Sampling rates are configured via Kibana agent config management. implements elastic#3487
simitt
added a commit
to simitt/apm-server
that referenced
this issue
Mar 16, 2020
Support fetching Jaeger gRPC sampling strategy from APM server. Only probabilistic sampling is supported. Sampling rates are configured via Kibana agent config management. implements elastic#3487
Thank you for the detailed write-up Silvia! Hope it's not too soon -- I've added documentation for this in #3493. |
simitt
added a commit
that referenced
this issue
Mar 18, 2020
Support fetching Jaeger gRPC sampling strategy from APM server. Only probabilistic sampling is supported. Sampling rates are configured via Kibana agent config management. implements #3487
simitt
added a commit
to simitt/apm-server
that referenced
this issue
Mar 18, 2020
Support fetching Jaeger gRPC sampling strategy from APM server. Only probabilistic sampling is supported. Sampling rates are configured via Kibana agent config management. implements elastic#3487
simitt
added a commit
that referenced
this issue
Mar 18, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As part of #3011 add the gRPC Jaeger sampling endpoint to the APM Server acting as Jaeger collector.
The endpoint will only support probabilistic sampling and should fetch the sampling rates from Kibana's agent configuration management.
By default the Jaeger sampling rate should be set to 100%.
Sampling in Jaeger tracing behaves different than Elastic APM sampling. Elastic APM currently always records 100% of transactions to allow a correct calculation of Requests per minute. Jaeger tracing only samples the configured percentage of transactions and spans, as there is no dedicated concept of transactions. If users configure a sampling rate smaller than 1, it will lead to incorrect values in the APM UI. We need to ensure this caveat is documented (cc @bmorelli25 ).
Why do we want to support sampling given this caveat?
Without the support of the sampling endpoint users that rely on sampling are excluding from using the Jaeger integration. With this change they can not depend on the Requests per Minute visualization, but can still make use of other Elastic APM features.
The text was updated successfully, but these errors were encountered: