🙏 Completely stopping a RUM recording session manually

[n-ochs]

What are you trying to achieve and what is your issue? Please describe.
Using @datadog/browser-rum - we currently start a session when a user logs into our application and we would like to completely stop their session when they log out. This way, when they log in again, a new RUM session is created along with the recording. According to the docs, this is not possible. I have tried stopSessionReplayRecording() and stopSession() while having the manual setting turned on. Both did not work.

Describe the solution you'd like
An API to completely stop the session recording, in which a new session recording is created when it is started again.

Describe alternatives you've considered
I've considered deleting the cookie upon user logout. I've tested it and it works, but I don't know if that it the correct solution or intended use of the API. Please advise.

[cy-moi]

Hi @n-ochs ,
Thank you for reaching out. Are you looking for something that stops the session from being recreated for logged-out users?

If it is, you can try setting trackingConsent as you need (public docs).

[n-ochs]

@cy-moi

No, I am looking for a way to start my RUM recording sessions when the user logs in and completely stop the RUM recording session when they log out. If the user logs in again, they should get a completely new session recording. I think the only way to make this work is to delete the DD cookie upon logout.

[amortemousque]

Hello @n-ochs,

I need a bit more detail to give proper guidance:

• When users log in and out, does your app stay on the same SPA route, or do you navigate to a different page or domain?
• Why do you need to force-stop RUM sessions instead of letting anonymous sessions cover the logged-out state?

From your description, it sounds like you want your application session and the RUM session to align one-to-one. At the moment, the Browser RUM SDK provide API to do so.

Here is more context on our session management that might help:

• stopSession() ends the current session, but the SDK will automatically start a new session as soon as it detects user interaction. Because of that, calling stopSession() at logout will not keep the session “off” and a new one starts almost immediately if the user stays on the same page.
• In addition, sessions automatically renew after 15 minutes of inactivity. If your user stays on the page while still logged in, the SDK would create a second session even though the user never logged out.