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

tracing: Add support for B3 headers via the JAEGER_PROPAGATION env var #1456

Merged
merged 1 commit into from
Jun 12, 2019

Conversation

ptescher
Copy link
Contributor

@ptescher ptescher commented Jun 1, 2019

This will provide compatibility with istio.

Fixes #1447

@CLAassistant
Copy link

CLAassistant commented Jun 1, 2019

CLA assistant check
All committers have signed the CLA.

@ptescher ptescher changed the title Add support for B3 headers via the JAEGER_PROPAGATION env var tracing: Add support for B3 headers via the JAEGER_PROPAGATION env var Jun 5, 2019
Copy link
Member

@aeneasr aeneasr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm very sorry for the late reply. I get so many notifications that sometimes things slip my radar. Thank you for the patch, I think it's on a good path but needs some changes before merging.

var configs []jeagerConf.Option

// This works in other jaeger clients, but is not part of jaeger-client-go
if os.Getenv("JAEGER_PROPAGATION") == "b3" {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please, instead:

  1. Add Propagation string to JaegerConfig
  2. Use the Propagation value here (t.JaegerConfig)
  3. Set the value here
  4. Document the new value around here
    To stay compatible it probably makes sense to do something like (assuming JAEGER_PROPAGATION is a de-facto standard):
Propagation: stringsx.Coalesce(
  viper.GetString("JAEGER_PROPAGATION")
  viperx.GetString(v.l, "tracing.providers.jaeger.propagation", ""),
),

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pushed some new changes, let me know if that works. I also added TRACING_PROVIDER_JAEGER_PROPAGATION just for consistency.

@ptescher ptescher force-pushed the feature/b3-headers branch from fc850a3 to 591d653 Compare June 8, 2019 16:26
ptescher added a commit to ptescher/x that referenced this pull request Jun 10, 2019
@ptescher ptescher mentioned this pull request Jun 10, 2019
5 tasks
aeneasr pushed a commit to ory/x that referenced this pull request Jun 11, 2019
@aeneasr
Copy link
Member

aeneasr commented Jun 11, 2019

Your changes to ory/x are now released as v0.0.61

@aeneasr
Copy link
Member

aeneasr commented Jun 11, 2019

ps: If you rebase on master, the module changes should be up to 0.0.61

This will provide compatibility with istio.
@ptescher ptescher force-pushed the feature/b3-headers branch from 591d653 to 2d290fc Compare June 11, 2019 17:21
@ptescher
Copy link
Contributor Author

@aeneasr all done, tests are passing now.

@aeneasr
Copy link
Member

aeneasr commented Jun 12, 2019

Awesome, thank you!

@aeneasr aeneasr merged commit 400c47f into ory:master Jun 12, 2019
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

Successfully merging this pull request may close these issues.

Support Jaeger Tracing with Istio and Kubernetes
3 participants