- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- FAQs
- Overview
- Permissions
- Pod Startup Fails Because the Envoy Sidecar Is Unready
- Envoy Converts Headers to Lowercase
- Headless Service-related FAQs
- Istio-init Crashes
- VirtualService Does Not Take Effect
- Inappropriate VirtualService Route Matching Order
- Failed to Access an Ingress Gateway from the Public Network
- Parsing Fails After Smart DNS Is Enabled
- Locality Load Balancing Does Not Take Effect
- Sidecars Are Not Automatically Injected
- Circuit Breaking Does Not Take Effect
- Service Is Abnormal Due to a Retry Policy
- Incomplete Call Tracing Information
- TCM Policy
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- FAQs
- Overview
- Permissions
- Pod Startup Fails Because the Envoy Sidecar Is Unready
- Envoy Converts Headers to Lowercase
- Headless Service-related FAQs
- Istio-init Crashes
- VirtualService Does Not Take Effect
- Inappropriate VirtualService Route Matching Order
- Failed to Access an Ingress Gateway from the Public Network
- Parsing Fails After Smart DNS Is Enabled
- Locality Load Balancing Does Not Take Effect
- Sidecars Are Not Automatically Injected
- Circuit Breaking Does Not Take Effect
- Service Is Abnormal Due to a Retry Policy
- Incomplete Call Tracing Information
- TCM Policy
- Glossary
Call tracing information displayed through the UI is incomplete, for example, information about a previous or next call trace is absent.
Cause
In most cases, it is because the HTTP headers required for tracing are not passed correctly or not passed at the service layer.
Using call tracing in Istio does not mean that services are non-intrusive. There is a basic requirement that a service needs to pass a received tracing-related header to a called service. This step cannot be done by Istio because Istio cannot perceive your service logic and does not know the previous request to which the request for the service to call another service corresponds. Therefore, the service needs to pass the header, and finally the traces can be chained completely.
Yes
No
Was this page helpful?