Skip to main content

High Latency Path

2690384146.png

The High Latency Path figure lists the affected services in a particular path of traffic flow along with its dependent services. If there are any anomalies in the dependent services such as pods or containers that can be possible causes of increased response time in a path.

From the High Latency Path graph, you can view the following:

  • The Latency SLO data is measured based on the response time taken by each individual dependent service involved in a particular path.

  • Click Latency Breakdown to view the following quick chart:

2690385911

  • Latency Breakdown lists the path of high latency in which the service is affected by the anomaly.

  • It also lists the dependent services in a path with detected anomalies that caused an increase in latency and request count data.

  • You can also enable Show All Paths to view all the various paths with dependent services of a particular affected service detected with the anomaly.

2690389289.png

For example, the following image represents the services with anomalies for a selected path.

2690390757

  • It lists the number of paths with dependent services affected by anomalies. Among those various paths, Container Observability provides the path that has high latency of the services detected anomalies.

Note

Note:

  • In the Show All Paths option, you can choose a path to verify if the services are having anomalies.

  • You can view the details of the pod or container of each service in a path having high latency to analyze the metric health that could be one of the causes of high latency.

Latency Path Chart

2690384339

The High Latency Path Chart lists the increase in response time of SLO at a particular time compared to the configured SLO value. The latency path graph describes the following:

  • The first occurrence of SLO latency data

  • Maximum latency SLO

  • The recent occurrence of SLO latency data.

Related topic:

In this section: