-
Notifications
You must be signed in to change notification settings - Fork 648
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
Enable global propagator for AWS instrumentation #2598
Comments
ocelotl
added a commit
to ocelotl/opentelemetry-python-contrib
that referenced
this issue
Jul 19, 2024
ocelotl
added a commit
to ocelotl/opentelemetry-python-contrib
that referenced
this issue
Jul 23, 2024
ocelotl
added a commit
to ocelotl/opentelemetry-python-contrib
that referenced
this issue
Jul 24, 2024
xrmx
added a commit
to xrmx/opentelemetry-python-contrib
that referenced
this issue
Jan 24, 2025
* Enable global propagator for AWS instrumentation Fixes open-telemetry#2598 * Add entry point test case * Update instrumentation/opentelemetry-instrumentation-aws-lambda/pyproject.toml Co-authored-by: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com> * Add test for propagator * Fix entry point name * Update instrumentation/opentelemetry-instrumentation-aws-lambda/tests/test_aws_lambda_instrumentation_manual.py Co-authored-by: Emídio Neto <9735060+emdneto@users.noreply.github.com> * Try with ubuntu latest * Try with 24.04 * Fix propagator key * Fix lint * Revert ununtuns --------- Co-authored-by: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com> Co-authored-by: Emídio Neto <9735060+emdneto@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a continuation of #2573. After that PR got meged, we now need to refactor the AWS instrumentation to use the AWS Lambda propagator from the global propagator.
The text was updated successfully, but these errors were encountered: