github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

backport of commit 9c280f5041 (#17117) 

Co-authored-by: Rosemary Wang <915624+joatmon08@users.noreply.github.com>
Co-authored-by: David Yu <dyu@hashicorp.com>
backport/docs/address-multicluster-singledc-docs/hopefully-set-mallard
hc-github-team-consul-core 2023-04-24 18:15:30 -07:00 committed by GitHub
parent acfd7d74a8
commit 80e700542f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
website/content/docs/connect/distributed-tracing.mdx
View File

@ -234,8 +234,11 @@ config to take effect.
1. Requests through [Ingress Gateways](/consul/docs/connect/gateways/ingress-gateway) will not be traced unless the header
`x-client-trace-id: 1` is set (see [hashicorp/consul#6645](https://github.com/hashicorp/consul/issues/6645)).
1. Consul does not currently support interoperation with [OpenTelemetry](https://opentelemetry.io/) libraries due to
Envoy not yet having support.
1. Consul's proxies do not currently support [OpenTelemetry](https://opentelemetry.io/) spans, as Envoy has not
[fully implemented](https://github.com/envoyproxy/envoy/issues/9958) it. Instead, you can add
OpenTelemetry libraries to your application to emit spans for other
[tracing protocols](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/observability/tracing)
supported by Envoy, such as Zipkin or Jaeger.
1. Tracing is only supported with Envoy proxies, not the built-in proxy.