SaaS TCP Connectivity Test

If users complain of inaccessibility to VMware Workspace ONE UEM, you may want to check the quality of the network link (TCP connection) to the VMware Workspace ONE UEM. A flaky or latent TCP network connection to the VMware Workspace ONE UEM can sometimes deny access to the users, thus, adversely impacting their overall experience with VMware Workspace ONE UEM. To avoid this, periodically run the SaaS TCP Connectivity test, and check the health of the TCP connections to the VMware Workspace ONE UEM.

This is an external test that emulates a TCP connection to the VMware Workspace ONE UEM and reports the count of connections that were successful and the count of connections that failed. In addition, this test also throws light on how responsive the VMware Workspace ONE UEM is to TCP connection requests. In the process, the test reveals any break or slowness in the network connection to the VMware Workspace ONE UEM service.

Target of the test : A VMware Workspace ONE UEM

Agent deploying the test : A remote agent

Outputs of the test : One set of results for each SITE URL:Port monitored

First-level descriptor: SITE URL:Port

Configurable parameters for the test

Parameters	Description
Test period	How often should the test be executed
Host	The host for which the test is to be configured.
URLS	By default, this parameter is specified in the <Site_URL>:<Port> format. against this parameter. For example, your specification can be: cn1687.awmdm.com:NULL. You can even provide a comma-separated list of sites to be monitored. Note that the <Site_URL>:<Port> specified against this parameter will be the descriptor of this test.
Packets to be Sent	The number of packets to be transmitted during the test.

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
Successful connections	Indicates the number of TCP connections that were successful for this site.	Number
Failed connections	Indicates the number of TCP connections that failed for this site.	Number	A high value for this measure indicates a flaky/latent network connection.
Percent of failed connections	Indicates the percentage of connections that failed for this site.	Percent	Ideally, the value of this measure should be close to 0%.
Maximum latency	Indicates the maximum time taken by this site to respond to TCP connection requests that it receives.	Milliseconds	Latency being high denotes a problem. Poor latencies may be due to the site being overloaded or misconfigured. If the URL accessed involves the generation of dynamic content, backend problems (e.g., an overload at the application server or a database failure) can also result in an increase in latency.
Minimum latency	Indicates the minimum time taken by this site to respond to TCP connection requests that it receives.	Milliseconds	A significant increase in the minimum latency is often a sure sign of network congestion.
Average latency	Indicates the average time taken by this site to respond to TCP connection requests that it receives.	Milliseconds