Web Timer Reports No Data

Use this page if you’ve set up a Chromium web application, but PerformanceGuard shows no data for it from Chrome or Edge.

Before you start

• You need the PerformanceGuard administrator role to check agent configuration groups and web applications.
• You need local administrator rights on an affected computer to check its registry.
• For background, see PerformanceGuard Web Timer Extension.

Check the web application

1. Select Administration → Network applications and open the web application.
2. Make sure the type is Chromium. The HTTP and IE types don’t use the browser extension.
3. Check that the Host value is part of the address users open, for example intranet.example.com.
4. Check that at least one RegExp matches the page path. For Chromium, the expression is matched against everything after the first / in the address, not the full address.

For details about the fields, see Web Applications.

Check the agent configuration group

1. Select Administration → Agent configuration → Configurations.
2. Select Edit next to the agent configuration group that the computer belongs to.
3. In the Network Report section, make sure Enable Chrome/Edge Extension as Local Machine Policy is selected.
4. In the Agent Service Parameters section, note the Web Server TCP port. The extension reaches the agent through this port on the local computer.
5. If you changed anything, select Save Configuration.

The agent applies the new configuration the next time it contacts the server.

Check the computer

1. On the affected computer, open the Registry Editor.

2. Check that the extension is in the browser’s force-install policy:

   • Chrome: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist
   • Edge: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist

   One of the values must contain leifiaolndnnmnkhmhibkejddgcfbfjf or gelgkjhdkdehhjeokbbkdplgkmhffnmc.

3. Check that the native messaging host is registered under HKEY_LOCAL_MACHINE\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.capasystems.performance. Edge also uses this Chrome registration.

4. In the browser, open chrome://extensions in Chrome or edge://extensions in Edge. Make sure the PerformanceGuard Web Timer extension is listed and turned on.

5. Open chrome://policy or edge://policy and check that the browser has applied the extension policies without errors.

Caution

The browser applies either machine policies or user policies for the extension list, not a mix. If your organization also deploys a user policy for force-installed extensions, the machine policy the agent writes can be ignored. See Configure Chromium based Browser Extensions.

If your organization restricts extensions or native messaging hosts with group policy, allow the extension IDs above and the native messaging host com.capasystems.performance.

Check what the extension received

This check only works if the agent configuration group also has Enable Chrome Extension Details selected, because only that variant has an options page.

1. In chrome://extensions or edge://extensions, open Details for PerformanceGuard Web Timer, and then open Extension options.
2. Under Configuration, check that your web application’s host is listed. If the section is empty, the extension couldn’t get its configuration from the agent. Check that the agent service is running and that its web server port isn’t blocked on the computer.
3. Open a page in the web application, and then refresh the options page. Last Match shows the web application and tag of the last page the extension reported.

Still no data

• Wait a few minutes. The extension checks for new configuration at most once a minute, and the agent sends its data at each report interval.
• If the icon shows load.. and never shows a time, the page never stops loading content. See Chrome Extension is stuck on loading.
• If the agent itself doesn’t report, see Agent Can’t Connect.