beta
/Detecting Cloud Service Latency Issues Through Analysis Of Tenant Latency Signals
Abstract

The techniques describe effective detection of latency-related issues for a cloud service operating in a distributed computing environment. To detect the latency-related issues, a system first determines baseline latency behavior at the tenant level (e.g., on a tenant-by-tenant basis) and compares a tenant's current latency behavior to the baseline latency behavior. If the comparison yields that the current latency behavior for the tenant is following the baseline latency behavior, the tenant is deemed healthy. However, if the comparison yields that the current latency behavior for the tenant is not closely following the baseline latency behavior, the tenant is deemed unhealthy. Once the system has made binary health determinations for various tenants on a tenant-by-tenant basis, the system is configured to aggregate the unhealthy determinations across a group of tenants to determine whether the cloud service is experiencing latency-related issues.

Full Text

What is claimed is:

The techniques describe effective detection of latency-related issues for a cloud service operating in a distributed computing environment. To detect the latency-related issues, a system first determines baseline latency behavior at the tenant level (e.g., on a tenant-by-tenant basis) and compares a tenant's current latency behavior to the baseline latency behavior. If the comparison yields that the current latency behavior for the tenant is following the baseline latency behavior, the tenant is deemed healthy. However, if the comparison yields that the current latency behavior for the tenant is not closely following the baseline latency behavior, the tenant is deemed unhealthy. Once the system has made binary health determinations for various tenants on a tenant-by-tenant basis, the system is configured to aggregate the unhealthy determinations across a group of tenants to determine whether the cloud service is experiencing latency-related issues.
Timeline
Filed
03/06/2026
Published
07/09/2026
Granted
Not Available
IPC Codes(2)
H04L 43/0888:Throughput
H04L 43/091:Measuring contribution of individual network components to actual service level