Abstract: Application and network tests executed for paths between endpoints and an application are proxied to reduce network traffic sent to application as part of synthetic testing. Testing for each endpoint behind a network element or security component acting as a test proxy for a path between the endpoint to the application is split into two segments: a segment from each endpoint to the test proxy, and a segment from the test proxy to the application. A service obtains test results from agents executing on the endpoints and the test proxy and “stitches” the results of each segment together to generate test results for the path from endpoint to application. Stitching refers to aggregating, combining, or otherwise joining the results obtained for each path segment to generate a set of test results for the path. The manner of stitching can vary depending on test type and/or types of performance metrics collected.

Abstract: An initial test is executed to determine an end-to-end latency of a path between a source and a destination. Subsequent tests incrementally target each node of the path for measurement of metric values indicative of delay of the nodes (e.g., latency, jitter, and packet loss). As tests are performed incrementally for each node, the maximum observed latency is tracked and used for calculating timeout thresholds. For the first hop, the timeout threshold is determined relative to the end-to-end latency; for subsequent hops, the timeout threshold is determined relative to the maximum non-timeout latency measured for a previous hop. Each test is performed N times to obtain additional values of delay metrics for each node. Upon completion of the N passes through the path, the resulting delay metric values determined for each test set are aggregated to yield a single, comprehensive result set.

Abstract: Performance tests targeting an application executing on a destination server and the network elements along the path thereto are executed by agents installed on multiple types of respective hosts across geographic locations. Agents execute incremental performance tests to identify network elements on the path and values of metrics indicative of network element delay and submit requests for accessing resources and/or invoke an API of the application to determine delay associated with accessing the application. The agents associate descriptive metadata with the test results before a central system obtains the test results and associated metadata for analysis to determine whether measured delay recorded in the results is indicative of a performance issue. If a performance issue is identified in a set of the results, the related metadata are evaluated to determine correlations between the results that provide further insight into the performance issue and affected end users of the application.

Abstract: An initial test is executed to determine an end-to-end latency of a path between a source and a destination. Subsequent tests incrementally target each node of the path for measurement of metric values indicative of delay of the nodes (e.g., latency, jitter, and packet loss). As tests are performed incrementally for each node, the maximum observed latency is tracked and used for calculating timeout thresholds. For the first hop, the timeout threshold is determined relative to the end-to-end latency; for subsequent hops, the timeout threshold is determined relative to the maximum non-timeout latency measured for a previous hop. Each test is performed N times to obtain additional values of delay metrics for each node. Upon completion of the N passes through the path, the resulting delay metric values determined for each test set are aggregated to yield a single, comprehensive result set.