-
Notifications
You must be signed in to change notification settings - Fork 525
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
docs: Tail-based sampling #7317
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
docs/sampling.asciidoc
Outdated
Sampling does not impact aggregated transaction and span <<data-model-metrics,metrics>>. | ||
This means that the visualizations in the APM app, like latency, throughput, time spent by span type, failed transaction rate, | ||
errors, error rate, etc., will always accurately reflect *all* of your application's requests, | ||
regardless of the configured sampling rate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might be a bit of an overstatement. Sampling may affect accuracy of latency.
Metrics are based on the sampled traces, and weighted by the inverse sampling rate. e.g. if you are sampling at 5%, then each trace will be counted as 20. Thus, as variance of latency increases, or the sampling rate decreases, your level of error will increase.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm. Updated. I'm still a bit confused about this so please let me know if it still needs work (likely).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The current wording sounds good.
Circling back to this now that PTO and |
docs/sampling.asciidoc
Outdated
Sampling does not impact aggregated transaction and span <<data-model-metrics,metrics>>. | ||
This means that the visualizations in the APM app, like latency, throughput, time spent by span type, failed transaction rate, | ||
errors, error rate, etc., will always accurately reflect *all* of your application's requests, | ||
regardless of the configured sampling rate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The current wording sounds good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a couple minor comments, but otherwise looks good. Feel free to merge after addressing the last bit.
@elasticmachine, run elasticsearch-ci/docs |
Co-authored-by: Silvia Mitter <silvia.mitter@elastic.co> (cherry picked from commit e6b435e)
Summary
This PR adds tail-based sampling documentation.
I tested the feature by spinning up an 8.1 instance on ESS and pointing APM integration testing at it:
Preview this PR
Related