When using distributed tracing, why need OC_AGENT_HOST=collector.linkerd-jaeger:55678 #7972
-
|
I saw in the version 2.11 doc kubectl -n emojivoto set env --all deploy OC_AGENT_HOST=collector.linkerd-jaeger:55678 This address is already configured in linkerd proxy. Why should the application need additional configuration? What is the use of this configuration？ |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
That configuration enables tracing in the emojivoto application so that jaeger includes spans from both the application and the proxies. Note, also, that Linkerd will never make tracing decisions independently. That is, it's up to something else (an ingress, the application, etc) to decide to trace a given request/span. Linkerd will honor this decision and participate in tracing, but the proxy will never trace a request that does not already have trace information. |
Beta Was this translation helpful? Give feedback.
-
|
thanks for the response! got it . |
Beta Was this translation helpful? Give feedback.
That configuration enables tracing in the emojivoto application so that jaeger includes spans from both the application and the proxies.
Note, also, that Linkerd will never make tracing decisions independently. That is, it's up to something else (an ingress, the application, etc) to decide to trace a given request/span. Linkerd will honor this decision and participate in tracing, but the proxy will never trace a request that does not already have trace information.