on - edited on by
HannahM
Summary: Occasionally, after enabling RUM, a website may experience issues. This article explains how to identify the problem and outlines the necessary configuration steps to resolve it.
- Problem
- Troubleshooting steps
- Is it a RUM issue?
- Change the injection point
- Change the capturing settings
- The behavior only affects XHRs
- What's next
Problem
You've just turned on RUM (automatic or manual injection), and you start noticing that your website is affected, possibly with some buttons not working or the website loading incorrectly.
Troubleshooting steps
Is it a RUM issue?
To check, 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. Right-click on the request, select 'Block Request URL', and then reload the page. The ruxitagent request should appear as blocked. If the issue persists, then this is an agent issue related to the technology and not a RUM issue, but if the problem is not there anymore, continue following the guide:
Change the injection point
The first step is to change where the injection is placed. We recommend the following:
- Inject after <head>
- Inject after <body>
- Inject before </body>
Note: For manual injection, there is no way to change the location through the UI; you need to change it in the source code.
For automatic injection, go to: Applications -> example_app -> settings -> Injection.
Change the capturing settings
If after changing the injection location, the issue still persists, then it might be a functionality issue. Here are some steps to take so that the problem can be narrowed down (if you're 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, so that way you can pinpoint what setting is causing the problem.
- 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, so that you can pinpoint what setting is causing the problem.
- Go to Applications -> example_app > Settings > General Settings > Enablement and cost control > disable "Enable Session Replay"
- Go to Applications -> example_app > Settings > Behavior analytics > Usability analytics > disable "Detect Rage Clicks"
The behavior only affects XHRs
If the behavior only affects XHRs, then enable "Use Proxy API for XHRs", wait a few minutes for the changes to take effect, and then check if the issue is resolved.
Note: For manual injection, some injection formats don't automatically apply settings changes made on the UI. When making a change in the settings, you need to replace the line of code that you inserted with the newly generated one.
What's next
If, after performing the above, the issue is still occurring, open a chat or contact support and provide
- a HAR file
- a screenshot of the console (if an error is generated there)
- If possible, record a small video of the behavior
- the troubleshooting steps you have already tried
What to read next:
