-
Notifications
You must be signed in to change notification settings - Fork 99
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
Feature request: Lambda Telemetry API support #94
Comments
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 |
I'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. |
+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.
The text was updated successfully, but these errors were encountered: