Installing the Edge Browser Extension
uberAgent’s browser web app performance functionality requires a browser extension to be installed. This article lists the necessary steps.
To enable data collection from Edge make sure uberAgent’s
BrowserPerformanceEdge metric is enabled in the configuration. In the default configuration,
BrowserPerformanceEdge is enabled.
The extension is available from the Chrome Web Store 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.
For tests and PoCs, it may be easiest to install uberAgent’s Edge extension manually from the Chrome Web Store. Please note that you need to allow extensions from other stores.
Install the extension from release channel on the Chrome Web Store.
Install the extension from beta channel on the Chrome Web Store.
Deployment of uberAgent’s Edge extension is easily possible with Group Policy. Follow the steps in the Edge documentation to configure the ExtensionInstallForcelist setting. Extensions on the
ExtensionInstallForcelist will also get installed if the Edge setting
Allow extensions from other stores is not enabled.
To configure Edge to install the uberAgent extension from the standard Chrome Web Store update URL add the following to the
Note that using the offline deployment you need to push updated CRX files manually.
uberAgent’s Edge extension uses native messaging to communicate with the agent. In a default configuration of Edge, native messaging is not restricted.
If native messaging has been restricted, for example via the NativeMessagingBlocklist Group Policy setting, an exception needs to be defined for the uberAgent extension, for example via the NativeMessagingAllowlist Group Policy setting.