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

code changes to resolve conditional server span creation for WSGI and adding 'attributes' parameter to util function #903

Conversation

sanketmehta28
Copy link
Member

@sanketmehta28 sanketmehta28 commented Feb 5, 2022

…tps://github.com//issues/454)

Description

This PR contains code changes for conditional server span creation for WSGI framework in case of another framework is present and it has already created SERVER span. In that case WSGI instrumentation will create a span of kind INTERNAL and make it a child of the SERVER span mentioned above.
Also I have added 'attributes' parameter to a util function _start_internal_or_server_span() util function to make it more compatible with multiple frameworks

Fixes # (issue)

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

  • Test A: Provide an unit test where a SERVER span was already exists in the context and check if the newly created span is of kind INTERNAL and is it a child of SERVER span mentioned before.

Does This PR Require a Core Repo Change?

  • No.

Checklist:

See contributing.md for styleguide, changelog guidelines, and more.

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

@sanketmehta28 sanketmehta28 requested a review from a team February 5, 2022 19:57
@sanketmehta28 sanketmehta28 changed the title code changes to resolve conditional server span creation for WSGI (ht… code changes to resolve conditional server span creation for WSGI and adding 'attributes' parameter to util function Feb 7, 2022
@sanketmehta28
Copy link
Member Author

@owais Can you please run the benchmark job again as this is flaky issue?

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.

3 participants