experimental AWS Lambda Function support #70
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kezhenxu94
reviewed
Feb 22, 2022
kezhenxu94
approved these changes
Feb 22, 2022
|
Will merge when main sw repo accepts component IDs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Explicit AWS Lambda Function plugins in their own
aws/subdirectory. Manual wrapping of AWS handler functions is required (much like the Azure Functions plugin), see the README. The following have been added:AWSLambdaTriggerPlugina generic wrapper which should work with all types of function triggers, but at the cost of information and linking back to calling endpoint.AWSLambdaGatewayAPIHTTPspecific wrapper for GatewayAPI HTTP type triggers, stores HTTP info and status code and allows linking back to calling endpoint.AWSLambdaGatewayAPIRESTsame as above except for the GatewayAPI REST type trigger.agent.flush()mechanism for synchronizing on segment data send. This is needed for AWS Lambdas because AWS freezes processes in between invocations.ContextManager.removeTailFinishedContexts()to remove any finished spans from a context to break a parent-child chain which is invalid because sequential independent invocations of a handler are executed in inherited async contexts of previous runs instead of being executed hierarchically like most servers do (for AWS Lambda functions).I will send up the component IDs to the main
skywalkingrepo once tests are passed.