mPulse system metrics
mPulse provides built-in, system metrics that are automatically captured and stored in the mPulse beacon.
This table lists the mPulse system metrics that are common to most dashboards.
||Browser Cache Hit Rate||The ratio (0-100) of the number of browser cache hits to browser cache misses.||The Collect ResourceTiming Data option must be selected in your web app configuration on the Beacons tab.|
|CDN Cache Hit Rate||The ratio (0-100) of the number of requests that were CDN cache hits (that is the request did not go to the origin) to the total number of requests made to the Akamai network.|
|Request Compression Rate||The ratio (0-100) of the number of requests where compression was applied to the total number of requests.|
|Request Count||The total number of requests.|
|Byte Compression Rate||The percent reduction in total number of bytes as a result of compression.|
|Decoded Body Size||The size received from the fetch (HTTP or cache) of the message body, after removing any applied content-codings (decodedBodySize).|
|Transfer Size||The size of the fetched resource including the response header fields plus the response payload body (transferSize).|
|Session||Session Duration||The amount of time the user spent in a single visit.||None|
|Session Length||The number of pages the user viewed in this session up to and including the current page, but not including any pages viewed after this page in the same session.|
|Standard||Bounce Rate||The ratio (0-100) of number of sessions consisting of a single page view (bounces) to the total number of sessions.||None|
|User Experience||Rage Clicks||How many times the user repeatedly clicked the same region.||
|Cumulative Layout Shift (CLS)||Measures visual stability; how many times a user tries and fails to interact with an element on the page. For example, how many times the user repeatedly clicked the same region.||