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

helm:Add an example of how to use this chart to enable opentracing with jaeger #680

Closed
kevinjqiu opened this issue Dec 5, 2019 · 1 comment

Comments

@kevinjqiu
Copy link
Contributor

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,

@t-eckert 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
@t-eckert t-eckert transferred this issue from hashicorp/consul-helm Aug 24, 2021
lawliet89 pushed a commit to lawliet89/consul-k8s that referenced this issue Sep 13, 2021
* update changelog for health checks and update comments in values.yaml
@david-yu
Copy link
Contributor

david-yu commented Feb 23, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants