Tencent Cloud Mesh
- Release Notes and Announcements
- Announcements
- Getting Started
- Application Configuration
- Traffic Control
- Service HA
- Multi-cluster Disaster Recovery and Multi-active
- Security Reinforcement
- Operation Guide
- Mesh Instance Management
- Service Discovery Management
- Traffic Management
- Observability
- Access Management
- Extended Features
- FAQs
Incomplete Call Tracing Information
Last updated: 2023-12-26 15:31:01
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.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No