Repository navigation
Feature request: Lambda Telemetry API support #94
Description
Activity
Just a +1 here. It would be great to have this. Right now, our SAM Local invoke won't work if we have OpenTelemetry in use by our Lambdas.
A lot of other folks are dealing with this. See here: aws/aws-sam-cli#4570
Looks like it's not possible to use Localstack as a workaround either: localstack/localstack#9617
Reacted by Joel Scheuner, Dave Cardwell, Peipei Fang, karim, Pedro Cova, silvio doblhofer, MarcosDanielTorres-UALA and Uladzimir VasilyevI've had to emulate the telemetry API myself in order to properly execute our Lambda Extension, which is fine – but first-class support for something so crucial to the ecosystem would be warmly welcomed by the community.
Reacted by AJ Stuyvenberg, jordan gonzález, Joel Scheuner and Omid EIDIVANDI+1, this causes DataDog's lambda extension to hang indefinitely. I could potentially write conditional code to only run it when not running locally, but that kind of defeats the point of sam's local support. DataDog/datadog-lambda-go#176
Originally created by @hooverdc here. I wasn't able to move the issue so creating a new one and linking.
Describe your idea/feature/enhancement
I wish SAM CLI would support the Lambda Telemetry API
Proposal
Provide a mock endpoint similar to the Lambda Logs API in the Lambda runtime images.
SAM CLI would need support in RIE to make this achievable within the emulation images.