Skip to content
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

Document the nuances of dynamic sampling more completely #1004

Open
cartermp opened this issue Feb 22, 2024 · 0 comments
Open

Document the nuances of dynamic sampling more completely #1004

cartermp opened this issue Feb 22, 2024 · 0 comments
Labels

Comments

@cartermp
Copy link
Member

Today we don't document some of the subtleties and considerations of dynamic sampling like we could.

@kentquirk mentioned in slack regarding some potentially unexpected behavior about not sampling at goal throughput rates:

Usually because the cardinality of the key fields is too high and/or using too short an evaluation period (and we could explain this better!). Dynamic Sampling always keeps at least one sample of every possible key combination, so if, say, your key field cardinality is 2000, and your cycle time is 30 seconds, and you don't send at least 60K spans/second (30x2000), we can't push sample rates high enough to hit your goals.

There's likely other things that are important for people to know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant