-
Notifications
You must be signed in to change notification settings - Fork 123
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
Sampled session should span across app lifetimes #957
Comments
Actually, what might be a better fix would be to add an option to reuse the sampled rate from the previously expired session here:
Something like: self.init(
isInitialSession: false,
parent: expiredSession.parent,
startTime: startTime,
dependencies: expiredSession.dependencies,
isSampled: configuration.shouldInheritExpiredSessionSampling ? expiredSession.isSampled : <apply sampling>
) |
Hey @AvdLee! Thank you for your report. We have several conditions that define a user session lifecycle, we basically restart a new session after:
Your use case falls under that second condition, which prevents reporting the completion of the resource upload which last more than 15mns. It doesn't have to do with sampling and there is no easy fix sadly. We are considering several approaches to tackle this use case which will require discussion internally since our user session definition in RUM is crossplatform. I will keep the ticket open and keep you posted with any updates. |
Thanks @maxep, keep me posted! For now we've configured our own sample rate randomizer, trying to see whether that improves our insights. |
With an applied sample rate: if the user goes into a background and a new session starts after the user returns after ~30 minutes, it's now possible this new session won't be sampled.
This is the question I'm trying to answer:
I understood from @ncreated a potential fix would be to apply the sample rate as follows:
However, ideally, this would be handled as an option inside the SDK.
The text was updated successfully, but these errors were encountered: