Set up the RUM browser extension

The RUM browser extension provides a means of gathering Real User Monitoring data from SaaS-licensed third-party applications even when you don't have access to the underlying application servers or HTML page source. Examples of such applications are Office 365, Workday, Concur, Google Apps, Zendesk, or Confluence.

When to use the RUM browser extension

Typically, the easiest way to gather RUM data for your application is to install OneAgent on your application servers—full-stack monitoring, which includes Real User Monitoring, is then enabled by default, with no additional configuration required. If you don't have access to your application servers, you can follow the agentless RUM approach. With agentless RUM, you manually modify the HTML of each of your application's pages to include the pre-configured RUM JavaScript. You can do that via templates or a tag manager.

If neither the OneAgent nor the agentless RUM approach is feasible in your environment, for example, because you don't have access to the application servers or your app's HTML files, try the RUM browser extension.

The RUM browser extension can also enhance Session Replay playback, specifically in the following cases:

Add and configure the RUM browser extension

To set up the RUM browser extension

URL pattern matching

The URL injection pattern is a regex pattern that the RUM browser extension applies to the current URL. When the pattern matches, the extension injects the RUM JavaScript and begins gathering RUM data.

For example, if you open Outlook 365 in your browser, you see a URL similar to https://outlook.office.com/owa/?realm=mycompany.com&exsvurl=1&ll-cc=1033&modurl=0
If you define the outlook\.office\.com URL pattern, the regex matches and the extension gathers RUM data for this page. Note that this same regex pattern is not a match for the Office 365 homepage, which can be https://www.office.com/?auth=2&home=1.

There are several online tools available to test your regular expressions, for example, Regex101.

You can modify the URL injection pattern at any time via the application settings: on the application overview page, select More (…) > Edit > Setup.

Configuration endpoint

There is an API endpoint that the RUM browser extension uses to get the current list of configured applications. The extension automatically fetches the latest configuration every 10 minutes.

You can check your configuration endpoint via your application settings: on the application overview page, select More (…) > Edit > Setup. The configuration URL is available under URL used by the browser extension to fetch the configuration.

Test your configuration

Open a new browser tab, and visit the configured application. You should see that the Dynatrace icon on the browser toolbar shows up in full color. The colored icon means that the extension has injected the RUM JavaScript and monitoring of the page is underway. If you switch back to Dynatrace, you should see the first user actions coming in. Select View application to get to the application overview page.

If you've downloaded the extension via the Dynatrace web UI, the extension is set to Admin mode. Admin mode enables you to edit the configuration URL by selecting the Dynatrace icon on your browser toolbar. This mode is intended for Dynatrace admins to test the extension and configuration before deploying the extension company-wide.

Select either Connect applications or Fetch configuration to fetch the latest application configuration from your Dynatrace environment.

Deploy the RUM browser extension for Google Chrome

After testing your configuration, you can deploy the extension either company-wide or for a specific group of users. This section explains how to configure Google Chrome through registry entries and provides hints on how to roll them out via group policy configurations in an enterprise environment.

Configure required properties

To deploy the RUM browser extension

For Windows, the best option is to use Windows group policies to set these policies.

Example of required registry entries

1[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist]
2"1"="fklgmciohehgadlafhljjhgdojfjihhk;https://clients2.google.com/service/update2/crx"
3
4[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\fklgmciohehgadlafhljjhgdojfjihhk\policy]
5"fetchUrl"="https://{your-environment-id}.live.dynatrace.com/api/v1/browserextension/config?Api-Token={your-token}"
6"adminMode"=dword:00000000

Configure additional properties

You can add additional optional properties to the registry.

To provide a company-wide external user policy link in the pop-up window of the RUM browser extension, set externalLink = http://<your-company-website-url> and nameOfExternalLink = <your policy link name>.

Example of optional registry entries

1[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\fklgmciohehgadlafhljjhgdojfjihhk\policy]
2"externalLink"="http://www.your-company-website.com"
3"nameOfExternalLink"="End User Privacy Policy"

The pop-up window of the RUM browser extension should look like this:

Verify your deployment

To verify a successful deployment and correct configuration of the RUM browser extension, follow the hints below.

Deploy the RUM browser extension for Microsoft Edge

You might want to deploy the extension company-wide or for a specific group of users. Check the sections below to learn how to configure Microsoft Edge through registry entries.

Configure required properties

To deploy the RUM browser extension

For Windows, the best option is to use Windows group policies to set these policies.

Example of required registry entries

1[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist]
2"1"="mpioohaaamocbdblijfoeigkkadcekli;https://edge.microsoft.com/extensionwebstorebase/v1/crx"
3
4[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\mpioohaaamocbdblijfoeigkkadcekli\policy]
5"fetchUrl"="https://{your-environment-id}.live.dynatrace.com/api/v1/browserextension/config?Api-Token={your-token}"
6"adminMode"=dword:00000000

Configure additional properties

You can add additional optional properties to the registry.

To provide a company-wide external user policy link in the pop-up window of the RUM browser extension, set externalLink = http://<your-company-website-url> and nameOfExternalLink = <your policy link name>.

Example of optional registry entries

1[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\mpioohaaamocbdblijfoeigkkadcekli\policy]
2"externalLink"="http://www.your-company-website.com"
3"nameOfExternalLink"="End User Privacy Policy"

The pop-up window of the RUM browser extension should look like this:

Verify your deployment

To verify a successful deployment and correct configuration of the RUM browser extension, follow the hints below.