Managing the Web Site/Web Application to be Monitored

Now that the required collectors have been installed and configured, let us now proceed to manage the web site/web application to be monitored and assign one of the configured collectors to it.

Note:

A collector that is not SSL-enabled cannot manage an SSL-enabled (i.e., an HTTPS) web site/web application. However, a collector that is SSL-enabled, can manage both HTTP and HTTPS web sites/web applications.

For this, follow the steps below:

  1. In the eG administrative interface, select the Add / Modify option from the Components menu in the Infrastructure tile.

  2. Figure 1 will then appear.

    Choosing to add Real User Monitor

    Figure 1 : Choosing to add a Real User Monitor

  3. Select Real User Monitor as the Component type from Figure 1 and click the Add New Component button to add a new component of that type.

  4. When Figure 2 appears, provide a unique name for the web site/web application that you want to monitor in the Nick name text box.

    Figure 2 : Adding a Real User Monitor

  1. Then, select the RUM collector you want to assign to the specified web site/web application. By default, the Nick Name (see Figure 2) of each of the RUM collectors that you have configured in your environment will populate the RUM collector drop-down in Figure 2. From this drop-down list, select the nick name of the RUM collector that you want to assign to the web site/web application being managed.
  2. Next, select the Remote agent that should monitor the web site/web application being managed by polling the selected collector.

  3. Then, click the Add button in Figure 2 to add the Real User Monitor component. Doing so will invoke . allows you to select the type of source file into which the eG RUM code snippet should be injected. If the HTML option is chosen, then the text area below will automatically display the HTML code snippet that you should include in any HTML/JSP/ASPX page that you want to instrument for user experience monitoring. Take care to include the displayed snippet after the head tag in the target pages.

    Figure 3 : Viewing the HTML code snippet to be injected into the monitored web pages

  4. On the other hand, if you choose the Javascript option, then the text area below will automatically display the code snippet that should be included in the *.js files that you want to instrument.

    Figure 4 : Viewing the Javascript code snippet to be injected into the monitored web pages