Assigned
Status Update
No update yet.
Comments
dh...@google.com
dh...@google.com
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
Customers need a way to have only the trace context header propagation enabled, without having an istio-proxy report spans to cloud trace? or a way to customize the spans on ASM trace
What you expected to happen:
be able to exclude istio spans in cloud trace
Steps to reproduce:
Other information (workarounds you have tried, documentation consulted, etc):
The traces for a service in Anthos Service Mesh contain following information:
Request latencies across different services in the mesh.
HTTP request properties, including ID, URL, size, latency, and protocol.
Service name, namespace and mesh id as part of the labels istio.canonical_service, istio.namespace, and istio.mesh_id, respectively.