Open vladholubiev opened 3 years ago
Hi @vladgolubev
Currently we can't reliably store all events of a session until some event happens. We are working on 2 solutions for this:
These 2 items are on the roadmap although we can't share any ETA for now.
@hdelaby, as this was ~6 months ago, I'm curious if "Enabling Error Tracking for browser logs" is still on the roadmap. We're comparing Sentry to Datadog, and as Sentry charges based on the number of error events, to get all errors with datadog we'd need 100% sampling which is the difference between ~$1k and ~$85k for us.
@hdelaby is there any update on this issue?
We are considering migration from sentry to datadog, and this issue make us frustrated because of cost issue
It's the 3 year anniversary of this issue being created, so I need to ask for an update as well now please. We want to use Datadog for effective tracking, but this issue is stopping us due to the phenomenal cost difference between being forced to track every single session to catch errors, and only storing "interesting" sessions with errors. Setting the sample rate lower and therefore missing errors is not an option.
Hi,
We are currently working on a feature that should help on that front. No precise ETA to share for now but stay tuned.
Hi @bcaudan, any further updates? Having an option to make RUM send sessions if an error/exception happens on the client-side would also be quite helpful for my project
Hi @arcticmatt, Unfortunately we do not have an ETA yet, but this is something that we're actively working on. Thanks for your patience
Right now we have lots of sessions collected. Only <1% of them have some error.
I'd like an option to configure RUM to send sessions if an error/exception happens on the client-side.
This will allow reducing spend greatly.