Autonomous DEM
Reusable Components
Table of Contents
Expand All
|
Collapse All
Autonomous DEM Docs
-
- AI-Powered ADEM
- Autonomous DEM for China
-
-
- AI-Powered ADEM
- Access Experience Agent 5.1
- Access Experience Agent 5.3
- Access Experience Agent 5.4
Reusable Components
Table of metrics collected using Real User Monitoring (RUM)
| Availability | Whether applications are reachable. |
| Page Load Time | The average time that a webpage takes to load. |
| Time To First Byte (TTTB) | The time it takes from when a user makes a request to a website until the browser receives the first byte of data. It measures how quickly the server responds to a request. |
| Largest Contentful Paint (LCP) | Reports the time it takes to render the largest image or block of text in the visible area of the web page when the user navigates to the page. |
| Cumulative Layout Shift (CLS) | Measures how stable the content of your webpage is as a user views it. The metric considers the unforeseen movement of elements within the visible area of the webpage during the loading process. |
| First Input Delay (FID) | Monitors the duration between a visitor's initial interaction with a web page and the moment the browser recognizes and begins processing the interaction. |
| Interaction to Next Paint (INP) | Monitors the delay of all user interactions with the page and provides a single value representing the maximum delay experienced by most interactions. A low INP indicates that the page consistently responded quickly to most user interactions. |
Elements from app test configuration topics
Network Test Options
| Field | Description |
|---|---|
| Protocol | Protocol to be used for network tests. It is set to TCP and cannot be changed. |
| Port | Set to port 443 which is the port that the TCP protocol uses. |
| Split Tunnel |
Select this check box if your application is split tunneled.
If you select the Split Tunnel option
along with selecting the Enable per hop performance
metrics option under Path
Visualization you will not be given the option
to select a Protocol under
Path Visualization. When you select
Split Tunnel, the protocol for split
tunnel applications will be chosen based on the operating system
where the access experience agent resides. The Windows agent
will run TCP-based traceroute for split tunnel applications,
hence the Protocol under Path
Visualization defaults to TCP on Windows. The
MacOS agents will run ICMP-based traceroutes for split tunneled
applications hence the Protocol defaults to ICMP on MacOS.
Selecting the Split Tunnel option along
with selecting the Enable per hop performance
metrics option under Path
Visualization shows per-hop network paths for
split tunneled applications in the Path Visualization
widget.
|