Browser Performance Metrics

Last published : Oct 14, 2026
Related information
Browser Metrics

All Chromium-Based Browsers

uberAgent collects performance data per Chromium-based browser process\. Data is collected per process type (e\.g\., Browser, Renderer, GPU, Utility, Extension) and includes per-website resource attribution through tab URL tracking\.
Note: Currently only Google Chrome and Microsoft Edge are supported\.

Details

  • Source type: uberAgent:Application:BrowserPerformance
  • Used in dashboards: Browser Resource Insights
  • Enabled through configuration setting: BrowserPerformanceChrome, BrowserPerformanceEdge
  • Related configuration settings: n/a
  • Supported platform: Windows, macOS

List of Fields in the Raw Agent Data

Field Description Data type Unit Measurement type Example
ProcUser User who ran the process. String Snapshot Domain\JohnDoe
Browser Numeric browser identifier. Resolved to BrowserDisplayName via lookup. Number Snapshot 1
ProcType Numeric process type identifier. Resolved to ProcTypeDisplayName via lookup. Number Snapshot 1
CPUPercent Average process CPU usage for the last interval (relative usage in percent). Number % Average 5.3
MemoryMB Memory sum of all processes for a TabUrl. Windows: Working set (memory) column in Task Manager macOS: Memory column in Activity Monitor. Number MB Sum 68.08
TabUrl Website URL associated with the renderer process. String Snapshot citrix.com
TabUrlCount Number of tabs with the same URL. Used to calculate per-website resource consumption. Number Snapshot 2
UtilityType Sub-type of Utility processes. Only populated when ProcType is 8 (Utility). String Snapshot network.mojom.NetworkService

List of Calculated Fields

Field Description Data type Unit Example Where available
BrowserDisplayName Browser name. Possible values: Chrome, Edge String Chrome Splunk data model, Splunk SPL
ProcTypeDisplayName Human-readable process type. String Renderer Splunk data model, Splunk SPL