Step 1: Check prerequisites to be done

1. Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager.
2. Refer the help page to know how to setup RUM Agent for Real User Monitoring.
   
3. Verify if the script generated in the respective RUM monitor details page is placed correctly on the webpage intended to be monitored.
   
4. Verify if the RUM agent protocol,  host name and port are specified correctly in the script in the below line.
   
1. (window,document,'agentprotocol://agenthost:agentport/RUMScript.js?appKey=','apmr','AfHowG5D62YOiWQHXp84DpV8eC2waN2E10000217');
   
2. Replace "agentprotocol" with the RUM Agent protocol 'http' or 'https' , based on the protocol to be used for collecting and sending data from end users to the RUM Agent. By default, RUM Agent supports only the HTTP protocol. To enable HTTPS, refer to the documentation for instructions..
   
3. Replace "agenthost" with the hostname where the RUM Agent is installed.
4. Replace "agentport" with the port number in which the RUM Agent is running. The port number should correspond to the agent protocol.

RUM Agent should be accessible to the end users visiting the webpage. You can check if RUM Agent is accessible or not by accessing http://agenthost:agentport in browser. Replace protocol, host and port with the agent details specified as in script.

Step 2: Check for connectivity error messages

1. Access the RUM Agent web console by opening (http://agenthost:agentport) in a browser.
   
2. Check the connectivity status message.
   

1. Open any browser and then open its developer tool, Click Networks tab and search for "rum" in the developer tool.
2. Access the webpage in which the script is placed i.e. webpage that is monitored in Applications Manager.
   
3. Request for RUMScript.js to RUM Agent should be sent successfully. Check the response of the RUMScript.js. 
4. If the request is not found please place the script properly and provide correct agent details in script as mentioned in above prerequisites.

Step 3: Troubleshoot using the provided error message

1. Check if AppManager is accessible from the machine where RUM Agent is installed.
   
2. Verify AppManager details provided in AppServer.properties file located under <RUMAgent_Home>/conf/ directory. 
3. Refer the KB to know how to change AppManager details in RUM Agent.
   
4. If Proxy is required to communicate with AppManager configure the same by referring the KB.
   
5. Check if RUM Agent is compatible for AppManager.

1. Make sure you use compatible version of RUM Agent for AppManager. Refer the download page to know the compatibility matrix.

1. Provide valid RUM API Key in AppServer.properties by referring the KB.
   
2. RUM API Key will present in Settings -> REST API -> Real User Monitor in Applications Manager.
   

1. Real User Monitor is not supported in Free edition of Applications Manager.
   
2. You need to purchase an license or use trial edition of Applications Manager.

1. You need to purchase an RUM addon for enabling RUM data collection. Refer the help page for pricing details.

1. Internal server error. Share SIF to analyze the issue.
   

1. We allow only certain amount of page views per month based on the license purchased.
   
2. When the page views have exceeded the limit allowed per month "PAGE VIEWS QUOTA EXCEEDED" message will be shown and data collection will be stopped.
   
3. Page views used count will be reset to zero on every month start.
   
4. Data collection will begin once page views used count is reset.

Purchase license based on your customer base to avoid above case.

1. Restart RUM Agent and check again.
2. Above message can also be seen when RUM Agent is trying to fetch monitor details from Applications Manager on RUM Agent startup. Wait till RUM Agent fetches RUM monitor details from AppManager.
   
3. Above message will be shown when the respective monitor is deleted in AppManager or key has been modified in the script injected in the webpage.
   
1. Note down the RUM monitor key from the script displayed in respective monitor details page in Copy Script Tab. Sample key AfHowG5D62YOiWQHXp84DpV8eC2waN2E10000217. Search for the same key in the script injected in the web page. If the key has been modified replace it with the exact key shown in respective monitor details page in Copy Script Tab.

Note : If the RUM monitor is mapped to specific RUM Agent, data collection can happen only in that specific agent.

Note: After making above changes if the data collection did not begin restart RUM Agent once and check the issue.

❌ Dont's

1. Placing multiple scripts in same webpage. It will affect RUM data collection.
   
2. Placing same script in multiple webpages. It will populate multiple webpage data in single monitor from where the script was taken.
   
3. Don't keep Applications Manager server down for long time. Applications Manager should be up for continuous data collection.

1. RUM Agent FAQS
   
2. How to get ISP data in Real User Monitor?
   
3. How to enable HTTPS connection between end user and RUM Agent?