Schedule demo

Configuring Real User Monitoring


The V2 RUM includes a simpler and smoother onboarding process by allowing users to skip the manual installation of the DEM Collector (formerly RUM Agent) by offering users a script that downloads the latest compatible DEM Collector for the Applications Manager version, installs the agent, starts it, and maps it to the tool.

Browse through the following topics to learn more about configuring V2 RUM:

Note: The DEM Collector communicates with Applications Manager once every minute. Data is collected only when the monitored website is accessed by clients.

Creating a new Real User Monitor

To create a new Real User Monitor, navigate to Add New Monitor → Web Server/Services → Real User Monitor, and enter the following details:

  1. Basic Details
    • Enter the website URL to be monitored.
    • Choose a name for the monitor of the website.
    • Specify Apdex Threshold (in ms) to be used to calculate the Apdex score and determine user experience.
    • Choose between Traditional/Single Page Application for the Application Type.

      Note: In Single Page Applications, each route change is counted as a page view.

    • Click on Next.
  2. Agent Configuration

    • Associate monitor instance with DEM Collector of your choice.

    Note: For each DEM Collector, we can add only up to 5 websites (5 monitors).

    • To deploy the DEM Collector click on the Want to deploy agent? option.
    • Choose between Windows and Linux as the OS in which you wish to deploy the agent.
    • Download the script file to be executed on the server where you want to install the DEM Collector. The script will automatically start the DEM Collector. If necessary, users can also choose to change the installation path before downloading it.

      • For Windows:
        Open PowerShell and run the following sample command:

        installdem.ps1

      • For Linux:
        Open a command terminal and run the following sample command:

        sh installdem.sh

      If you encounter any issues, please refer to this page.

    • Click on Next to complete monitor addition and move to the RUM Script Injection details.
  3. JS injection
    • Select Application: Select the application framework type (Node.js, PHP, .NET, Java, or others).
    • Application Types: Select the application subtype for the selected application (Eg: Subtypes for Node.js - Express and Pug, Express and Swig, Hapi.js and Handlebars, or others).
    • Script File: Copy the code snippet displayed and paste it into your HTML file to complete the script injection. Refer to this help page to learn more.
    • Click on Complete.
    • On completing the script injection, the page will be automatically redirected to the monitor details page.

Additional Configuration Options

Once a Real User Monitor is added, you can fine-tune its behavior from the Edit Monitor page. These options are not available during monitor creation but can be configured later if needed:

  • Track Ajax calls: Monitor the performance of asynchronous requests.
  • Track cross-domain Ajax calls: Monitor Ajax requests made to external domains.
  • Track IP Address: Monitor the IP address of users.
  • Domains to exclude: Specify domain names (e.g., zoho.com) to skip from tracking.
  • User agents to exclude: Filter out specific browser/OS types or full user-agent strings.
  • Track Resource Performance: Capture and group page resources as first-party, third-party, or CDN. Disabled by default.
  • Affect monitor availability in idle state: Monitor availability is affected when no data is polled beyond the idle timeout set under Settings → Availability Settings.
  • Capture JavaScript Errors: Enable to track client-side JavaScript errors. Disabled by default.

These configurations help you tailor Real User Monitoring to your specific requirements and refine data collection.

Starting the DEM Collector

Windows

  • Open command terminal from the newly-installed <DEMCollector_Home> directory. (Eg:C:\Program File\ManageEngine\DEMCollector)
  • Execute the StartServer.bat command in the terminal to start the DEM Collector.
  • Upon executing the command, the DEM Collector will start, and a new window will be opened in the browser displaying all DEMCollector-related information such as its agent version, hostname, port, and the connectivity status of the agent with the Applications Manager console.
  • You can stop the agent by executing the StopServer.bat -force command from command prompt.

Note:

  • Above steps are for non-service installations only. In the case of Service installations, you can start the DEM Collector directly by starting the ManageEngine DEM Collector Agent service from Windows Services.
  • In case you want to change Application Manager's instance details in DEM Collector after installation, refer here.

Linux

  • Open command terminal from the newly-installed <DEMCollector_Home> directory. (Eg:\home\test\ManageEngine\DEMCollector)
  • Execute the sh StartServer.sh command in the terminal to start the DEM Collector.
  • Upon executing the command, the DEM Collector will be started,d and a new window will be opened in the browser displaying DEM Collector information such as agent version, hostname, port, and the connectivity status of the agent with the Applications Manager console.
  • You can stop the agent by executing the sh StopServer.sh -force command from command terminal.

Note: 

< p> To install DEM Collector as a Linux service, you need to have root privileges on that system. The following steps are applicable only for DEM Collector version 4.4 and above:
  • Go to <DEMCollector_Home>/bin directory, execute the installService.sh file. On executing this file, the ManageEngine DEM Collector Agent service will be added to Linux services, and the startup type will be set to Automatic by default.
  • Now, when you start a Linux system, DEM Collector will start automatically. You can switch between Automatic and Manual modes.
  • To change Application Manager's instance details in the DEM Collector after installation, refer here.
  • To uninstall this service, go to <DEMCollector_Home>/bin directory and execute the uninstallService.sh file.

Uninstalling the DEM Collector

Note: Before uninstalling the agent, exit the command prompt and close all the files and folders opened in the < DEM Collector Home> directory. If the DEM Collector is running, stop the agent before uninstalling it to remove all related files completely.

Windows

  • If the DEM Collector is running, you should stop the agent before uninstalling it. You can stop the agent by executing the StopServer.bat -force command from the command prompt.
  • Open Control Panel → Uninstall Program → right click on Applications Manager - DEM Collector → Click Uninstall. Then follow the instructions shown on screen to uninstall the agent.

Linux

  • If the DEM Collector is running, you should stop the agent before uninstalling it. You can stop the agent by executing the sh StopServer.sh -force command from the command terminal.
  • Open terminal from <DEMCollector_Home>/_Applications Manager - DEM Collector_installation directory and execute "./Change\ Applications\ Manager\ -\ DEM\ Collector\ Installation" and follow the process.

Loved by customers all over the world

"Standout Tool With Extensive Monitoring Capabilities"

★★★★★

It allows us to track crucial metrics such as response times, resource utilization, error rates, and transaction performance. The real-time monitoring alerts promptly notify us of any issues or anomalies, enabling us to take immediate action.

Reviewer Role: Research and Development

carlos-rivero
"I like Applications Manager because it helps us to detect issues present in our servers and SQL databases."
Carlos Rivero

Tech Support Manager, Lexmark

Trusted by thousands of leading businesses globally