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

Add .NET lambda limitations to docs #2654

Closed
jaffinito opened this issue Jul 29, 2024 · 1 comment
Closed

Add .NET lambda limitations to docs #2654

jaffinito opened this issue Jul 29, 2024 · 1 comment

Comments

@jaffinito
Copy link
Member

Describe the story, please be clear on scope of the story.

We should add the limitations to our docs. maybe in the approaches doc. Since this is not migration related, that doc would not work. I looked over the serverless docs and none of them feel like a good fit.

Limitations:

  • Generic lambda Methods are not instrumented automatically. If your lambda method is a generic method (Such as Task MyMethod<TRequest, TResponse>(TRequest, ILambdaContext), the agent is not currently able to instrument that method.
  • AspNetCore lambdas are not supported. The lambda AspNetCore integration relies on a generic method that is registered as the lambda handler, and generic lambda methods are not supported yet.
  • Lambda Annotations Framework is not supported.
  • ApiGatewayV2 events are missing some context required for Distributed Tracing.
  • Outbound Distributed Tracing for different AWS SDK calls (such as SQS) are not supported.
  • If your lambda method does not include an ILambdaContext parameter, the agent will not be able to gather all of the expected information about your Lambda.
  • Native AOT .net lambdas are not supported.
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

No branches or pull requests

1 participant