You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the advantages of using consul connect (envoy to be more specific) is to have native integration with opentracing for the services. This allows us to have end-to-end traces on a high level, and later selectively implement higher fidelity instrumentations in the services.
I'm struggling to find a way to integrate this using the consul-helm chart. More specifically, the automatic span creation is done in envoy's listener section like so, but I'm not sure how that can be done with this chart, since service configuration is injected into the sidecar pod using annotations, and I haven't seen an annotation that allows me to inject envoy listener config per service.
An example would surely be appreciated. Note that I have tried consul-demo-tracing, but it doesn't use envoy to create the spans automatically.
Thanks,
The text was updated successfully, but these errors were encountered:
t-eckert
changed the title
Add an example of how to use this chart to enable opentracing with jaeger
helm:Add an example of how to use this chart to enable opentracing with jaeger
Aug 24, 2021
Hi @kevinjqiu we recently updated our docs to include an example on how to do distributed tracing with the OpenTracing libraries. You can use the Zipkin format to send traces over to the jaeger collector, whose url could be explicitly configured via the https://www.consul.io/docs/connect/proxies/envoy#envoy_extra_static_clusters_json key. Hope this helps, and will close for now.
One of the advantages of using consul connect (envoy to be more specific) is to have native integration with opentracing for the services. This allows us to have end-to-end traces on a high level, and later selectively implement higher fidelity instrumentations in the services.
I'm struggling to find a way to integrate this using the consul-helm chart. More specifically, the automatic span creation is done in envoy's listener section like so, but I'm not sure how that can be done with this chart, since service configuration is injected into the sidecar pod using annotations, and I haven't seen an annotation that allows me to inject envoy listener config per service.
An example would surely be appreciated. Note that I have tried consul-demo-tracing, but it doesn't use envoy to create the spans automatically.
Thanks,
The text was updated successfully, but these errors were encountered: