aws-powertools/powertools-lambda-python

Feature request: OpenTelemetry Support

Opened this issue · 3 comments

Use case

We're actively considering bringing OpenTelemetry support to Powertools for AWS Lambda 🎉

If this is something that you'd like to see us working on, please take some time to read this RFC aws-powertools/powertools-lambda#90 and share your feedback. If you prefer, you can also email us at aws-powertools-maintainers@amazon.com using your work email ;)

This RFC focuses on Tracer and all examples are in Python, but we really want to hear your opinion and make this the best possible OTEL experience on AWS Lambda!

Solution/User Experience

See aws-powertools/powertools-lambda#90

Alternative solutions

Acknowledgment

I think this is a great idea. To be completely honest, I am not a big fan of lambda layers (maybe I am using them wrong?) so I would rather have something that can be installed in the same way of all the other extra dependencies for this repo.

Hello, as you may be aware the AWS X-ray SDK now has a deprecation plan (it enters a maintenance mode in February, is EOL the February after), See Aws docs

I always hoped that the powertools would make the move from x-ray SDK to Otel as easy as possible, and I do believe that the RFC/proposal sets out a way in which it would be!

Now that we have to move to Otel, I need to consider a migration plan and what to recommend for new services going forward. As a Big Powertools Fan, that hinges on what powertools is going to do.

In light of the recent news, is the powertools team able to commit to something around OTel? I appreciate this has been in discussion for a couple of years now, so is there anything we as community and customers can do to help move this along?

Thanks ♥️

Hello, as you may be aware the AWS X-ray SDK now has a deprecation plan (it enters a maintenance mode in February, is EOL the February after), See Aws docs

I always hoped that the powertools would make the move from x-ray SDK to Otel as easy as possible, and I do believe that the RFC/proposal sets out a way in which it would be!

Yes, we wrote this RFC to raise awareness of this topic and gather community feedback to help us define the shape/future of this implementation. I'd really appreciate it if you could contribute to the RFC - of course, if you have any feedback and time allows.

Now that we have to move to Otel, I need to consider a migration plan and what to recommend for new services going forward. As a Big Powertools Fan, that hinges on what powertools is going to do.

I really love reading when our work makes a difference in other people's lives and people are happy with the project we are building.

In light of the recent news, is the powertools team able to commit to something around OTel? I appreciate this has been in discussion for a couple of years now, so is there anything we as community and customers can do to help move this along?

I imagine you're asking about dates/deadlines here, and we haven't committed to any specific dates yet, as there are many open questions in the RFC that we hope to have the proper answer soon. But this doesn't mean we're not working on them and trying to speed things up, but again, we need to have answers to some questions, and we don't have them yet.

We're also working closely with the Lambda/Observability Service team to find the best experience for customers using Lambda instrumentation with OpenTelemetry.

I'd love to connect with you in a meeting - you can bring your team if you'd like - to better understand your Powertools for AWS use case and also discuss OTEL. Customer influence/demand is extremely important so that we can use it in some requirements/decisions that we need to have internally.

If you'd like, you can email aws-powertools-maintainers@amazon.com and I'll send you some dates to meet. I'll be on PTO from the 16th to the 24th, but I can respond to your email within those dates.

Thanks ♥️

Thank you very much, I really appreciate your words and I will be very happy to help with whatever I can. ❤️ ❤️