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

botocore: Fix span inject for lambda invoke #663

Merged

Conversation

mariojonke
Copy link
Contributor

@mariojonke mariojonke commented Sep 7, 2021

Description

Span injection for lambda invoke in the botocore instrumentation happened before the botocore span was actually created which resulted in injecting the parent span instead of the actual botocore span.
This PR fixes span injection to inject the actual botocore span.

Type of change

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

How Has This Been Tested?

Adapted existing unit test

Does This PR Require a Core Repo Change?

  • No.

Checklist:

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

* for lambda invoke span injection happend to early which resulted in the botocore
  span being injected instead of the actual botocore span
@mariojonke mariojonke requested a review from a team September 7, 2021 14:08
@ocelotl ocelotl merged commit 3e9adfd into open-telemetry:main Sep 9, 2021
@mariojonke mariojonke deleted the botocore-fix-lambda-invoke-inject branch October 8, 2021 08:32
nstawski pushed a commit to nstawski/ns-opentelemetry-python-contrib that referenced this pull request May 10, 2023
…en-telemetry#1036)

This commit extends the instrument command so it automatically
configures tracing with a provider, span processor and exporter. Most of
the component used can be customized with env vars or CLI arguments.

Details can be found on opentelemetry-instrumentation's README package.

Fixes open-telemetry#663
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.

4 participants