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

adding support for Jaeger propagator #1219

Merged
merged 19 commits into from
Dec 8, 2020
Merged

Conversation

Rashmi-K-A
Copy link
Contributor

@Rashmi-K-A Rashmi-K-A commented Oct 8, 2020

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes #1103

Type of change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Unit tests

Checklist:

  • Followed the style guidelines of this project
  • Changelogs have been updated
  • Unit tests have been added

@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Oct 8, 2020

CLA Check
The committers are authorized under a signed CLA.

@codeboten
Copy link
Contributor

@Rashmi-K-A are you still interested in taking on this work? #1084 has been resolved which should unblock you.

@Rashmi-K-A
Copy link
Contributor Author

Hey, yes @codeboten, I noticed just today that it has been resolved. I'll get working and maybe have a PR ready by this weekend!

@Rashmi-K-A
Copy link
Contributor Author

Rashmi-K-A commented Nov 9, 2020

@codeboten The Jaeger format talks about a 'firehose' flag here. Should I be searching for a tag with a key name called firehose? I couldn't find enough information about it to implement that part.

@codeboten
Copy link
Contributor

@codeboten The Jaeger format talks about a 'firehose' flag here. Should I be searching for a tag with a key name called firehose? I couldn't find enough information about it to implement that part.

It's a good question, i don't see any mentions of this anywhere in the js implementation. Looking through spec issues i did find this one: open-telemetry/opentelemetry-specification#231

But it looks like it's targeted for after GA, so it's probably ok to skip the implementation here.

@Rashmi-K-A
Copy link
Contributor Author

@codeboten The Jaeger format talks about a 'firehose' flag here. Should I be searching for a tag with a key name called firehose? I couldn't find enough information about it to implement that part.

It's a good question, i don't see any mentions of this anywhere in the js implementation. Looking through spec issues i did find this one: open-telemetry/opentelemetry-specification#231

But it looks like it's targeted for after GA, so it's probably ok to skip the implementation here.

Cool, then I'll just add some final touches here and mark this PR as ready for review

@Rashmi-K-A Rashmi-K-A marked this pull request as ready for review November 10, 2020 15:28
@Rashmi-K-A Rashmi-K-A requested review from a team, toumorokoshi and hectorhdzg and removed request for a team November 10, 2020 15:28
for key in getter.keys(carrier)
if key.startswith(self.BAGGAGE_PREFIX)
]
for key in baggage_keys:
Copy link
Contributor

Choose a reason for hiding this comment

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

Worth adding support for the BAGGAGE_HEADER alternative (as a follow-up). See https://github.com/jaegertracing/jaeger-client-python/blob/master/jaeger_client/codecs.py#L116

@lzchen
Copy link
Contributor

lzchen commented Nov 12, 2020

@Rashmi-K-A
Can you change the description of the PR to remove the "Work in progress"?

Copy link
Member

@toumorokoshi toumorokoshi left a comment

Choose a reason for hiding this comment

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

Thanks! pretty good, I think there's a few lingering questions, maybe a couple blockers here (e.g. invalid parsing of flags)

@toumorokoshi
Copy link
Member

Also a changelog entry please!

Copy link
Contributor

@ocelotl ocelotl left a comment

Choose a reason for hiding this comment

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

Looking good! Just minor comments.

@lzchen
Copy link
Contributor

lzchen commented Nov 19, 2020

@Rashmi-K-A
Have @toumorokoshi 's and @ocelotl 's comments been addressed yet? This change is pretty urgent.

@Rashmi-K-A
Copy link
Contributor Author

Rashmi-K-A commented Nov 19, 2020

hey @lzchen, I haven't gotten around to completing all of these changes yet, I'll work on getting them done by this weekend!

Copy link
Member

@toumorokoshi toumorokoshi left a comment

Choose a reason for hiding this comment

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

Thanks for addressing some of the comments! I think there's some more work that could be done, but this looks to provide most of the desired functionality. Thanks!

@Rashmi-K-A
Copy link
Contributor Author

Rashmi-K-A commented Nov 25, 2020

I have made one final round of changes. The B3 filename and the classname must be changed, and the extract function it uses must be imported from init.py to prevent redundancy. I'll raise an issue for that once this PR is done.

@codeboten
Copy link
Contributor

@ocelotl & @carlosalberto please review and approve if your comments have been addressed!

@ocelotl
Copy link
Contributor

ocelotl commented Dec 3, 2020

My changes have been addressed, but the test cases are failing, @Rashmi-K-A please take a look.

Copy link
Contributor

@ocelotl ocelotl left a comment

Choose a reason for hiding this comment

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

Test cases are failing, please fix that @Rashmi-K-A 👍

@codeboten
Copy link
Contributor

@ocelotl if you're ok with the changes, please approve. we will block on merging until the tests pass!

@Rashmi-K-A
Copy link
Contributor Author

The test cases started failing after merging changes from master (which is weird because my code is in a file that's not even in master), I ll take a look within a couple of days.

Copy link
Contributor

@ocelotl ocelotl left a comment

Choose a reason for hiding this comment

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

I am ok with the changes, approving tests can be fixed before merging

@Rashmi-K-A
Copy link
Contributor Author

@codeboten I fixed the errors, it turns out the propagator wasn't implementing a function added to its parent class in a recent change. It's working now! Let me know if I missed out something

@lzchen lzchen merged commit 5eb0533 into open-telemetry:master Dec 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release:required-for-ga To be resolved before GA release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add support for Jaeger propagator
6 participants