uberAgent’s browser web app performance functionality requires a browser extension to be installed. This article lists the necessary steps.

Enabling the Agent Metric

To enable data collection from Chrome make sure uberAgent’s BrowserPerformanceChrome metric is enabled in the configuration. In the default configuration, BrowserPerformanceChrome is enabled.

Installing the Chrome Extension

The extension is available from two different channels: release and beta. The release channel gets only fully-tested versions of the extension, while the beta channel additionally gets beta-quality versions.

We recommend putting the majority of users on the release channel and a small minority on the beta channel.

Manual Installation

For tests and PoCs, it may be easiest to install uberAgent’s Chrome extension manually from the Chrome Web Store.

Release Channel

Install the extension from release channel on the Chrome Web Store.

Beta Channel

Install the extension from beta channel on the Chrome Web Store.

Automated Deployment

Deployment of uberAgent’s Chrome extension is easily possible with Group Policy. Follow the steps in the Chromium Documentation to configure the ExtensionInstallForcelist setting.

To configure Chrome to install the uberAgent extension from the standard Chrome Web Store update URL add the following to the ExtensionInstallForcelist setting:

Release Channel

cmcmennehclgdccnlmnjladhlkmclbkb;https://clients2.google.com/service/update2/crx

Beta Channel

lnjgkeibanadbijljjijogklikdblaom;https://clients2.google.com/service/update2/crx

Offline Deployment

If your endpoints are not connected to the Internet and can’t access Chrome’s Web Store, you can also pre-install the extensions. Please contact us for the CRX file or use an online CRX extractor.

Note that using the offline deployment you need to push updated CRX files manually.

Relevant Configuration Settings

Native Messaging

uberAgent’s Chrome extension uses native messaging to communicate with the agent. In a default configuration of Chrome, native messaging is not restricted.

If native messaging has been restricted, for example via the NativeMessagingBlacklist Group Policy setting, an exception needs to be defined for the uberAgent extension, for example via the NativeMessagingWhitelist Group Policy setting.