When session is not recorded, what we should check on the browser?

kanako_sato — Wed, 22 Nov 2023 13:32:01 GMT

When session is not recorded, please check the following 2 points on the browser.

1. Javascript agent is injected and loaded

Check the page source that JavaScript code is present and that it loads ruxitagentjs_* with 200 OK with valid contents (not empty).

Then, on browser developer tool, check if the following 2 Javascript agents should be loaded: normal js agent with feature hash Q, and a separate js agent with feature hash D like:

ruxitagentjs_ICA2Qfhqrx_10168190402130100.js
ruxitagentjs_D_10168190402130100.js

2. rb_ beacons are sent back successfully

On browser developer tool, check the session replay rb_bf POSTS (Content-Type : application/octet-stream) are sent with a 200 response code and successful response body: e.g., OK(nginx)|name=ruxitagentjs|featureHash=ICA2Qfhqrx|version=|buildNumber=10168190402130100|lastModification=1554225766831

On occasion, WAFs/firewalls/Load balancers will block these beacons.

Re: When session is not recorded, what we should check on the browser?

AntonioSousa — Sun, 27 Nov 2022 11:01:33 GMT

I would also suggest for RUM troubleshooting, the session with @Julius_Loman & @andreas_grabner
https://www.youtube.com/watch?v=cBQ_AF5J8m8

article When session is not recorded, what we should check on the browser? in Troubleshooting

When session is not recorded, what we should check on the browser?

Re: When session is not recorded, what we should check on the browser?