Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of Clarify OpenTelemetry support for tracing into release/1.15.x #17117

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions website/content/docs/connect/distributed-tracing.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down