Skip to content

Conversation

@Zylphrex
Copy link
Member

@Zylphrex Zylphrex commented Nov 3, 2021

Because of the use of count_unique(id) to compute the number of transactions
that contain the span, and that it is an approximation, it is possible that we
will see some frequency values exceeding 100%. This clips the frequency value so
that this never happens.

Because of the use of `count_unique(id)` to compute the number of transactions
that contain the span, and that it is an approximation, it is possible that we
will see some frequency values exceeding 100%. This clips the frequency value so
that this never happens.
Copy link
Member

@k-fish k-fish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm guessing that your note with count_unique(id) means you've confirmed that's the cause? if so then 👍

@Zylphrex Zylphrex merged commit 41d744c into master Nov 4, 2021
@Zylphrex Zylphrex deleted the fix/span-frequency-should-never-exceed-100% branch November 4, 2021 14:11
@github-actions github-actions bot locked and limited conversation to collaborators Nov 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants