Problem:
You've just turned on RUM (automatic injection or manual injection), and you start noticing that your website is affected, maybe some buttons stop working or the website is not loading correctly.
Troubleshooting steps:
Is it a RUM issue ?
To make sure it is, there is a simple test to be done at the start, which is blocking the ruxitagent request in the network tab and reloading the page, simply right click on the request -> block request URL -> Reload the page. The ruxitagent request should appear as blocked, if the issue still persists then this is an agent issue related to the technology and not a RUM issue, but if the issue is not there anymore continue following the guide:
1- The first step here would be to change where the injection is placed, we recommend the following:
- Inject after <head>
- Inject after <body>
- Inject before </body>
For manual injection there is no way to change the location through the UI, you must change it in the source code.
For automatic injection, go to: Applications -> example_app -> settings -> Injection
2- If after changing the injection location the issue still persists then it might a functionality issue. Here are some steps to take so that the problem can be narrowed down (if you are using manual injection please check the note at the bottom of this article before continuing).
- Go to Applications -> example_app -> settings -> Capturing -> Async web requests and SPAs, disable the settings on that page and wait for 10 minutes and check if the issue persists on the website:
- If the issue is gone, then re-enable the settings one by one while testing the website that way you would pinpoint what setting is causing the issue.
- If the issue persists, re-enable the previous settings and go to Applications -> example_app -> settings -> Capturing -> Content capture and disable the settings there and wait for 10 minutes and check if the issue persists on the website:
- If the issue is gone, then re-enable the settings one by one while testing the website that way you would pinpoint what setting is causing the issue.
Is the problem only affecting XHRs ?
- If so then please try and enable "Use Proxy API for XHRs", wait for a few minutes for the changes to take place and then check if the issue is fixed.
If after performing the above the issue is still occurring please collect a HAR file, a screenshot of the console (if an error is generated there), and possible record a small video of the behavior, and open a support ticket.
Note: For manual injection, some injection formats do not automatically apply settings changes done on the UI, when making a change in the settings you must replace the line of code that you inserted with the newly generated one.
