Add serverless mode support to Profiler #2285
Merged
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.
This adds the ability to add an instrumentation point to the Profiler via an environment variable,
AWS_LAMBDA_FUNCTION_NAME
, in the formatassembly::class::method
. If the variable is not in the correct format it will log a Warning but continue running. It does not attempt to verify that the method exists.The environment variable can be added at any point during the startup sequence and the Profiler will pick it up (as long as the method hasn't been invoked yet)..
When the named method is invoked it will call the wrapper
NewRelic.Providers.Wrapper.AwsLambda.HandlerMethod
in the managed Agent.Unit tests are included.
This also removes the hard-coded method name in the
instrumentation.xml
that was used in the POC branch.