Description
In serverless mode, entities are not determined via app name but via the lamnda ARN. Per agent specs, app names are not reported in the serverless payload. As a result app naming should not be required and auto app naming should be disabled.
Since the agent's functionality requires an app name, there should exist a default app name for serverless mode. Some criteria for app naming may include the following:
- Lambda's arn if accessible outside a lambda invocation call
- A default static string such as "serverless-mode-function".
The app name should still be configurable.
Acceptance Criteria
Auto app naming is automatically disabled in serverless mode. In addition, there should be a default (yet overridable) app name when serverless mode is enabled.
Design Considerations
Code changes in the agent are not always necessary. One workaround that can be considered is naming the application with a lambda layer startup script but allow it to be overridable.
Description
In serverless mode, entities are not determined via app name but via the lamnda ARN. Per agent specs, app names are not reported in the serverless payload. As a result app naming should not be required and auto app naming should be disabled.
Since the agent's functionality requires an app name, there should exist a default app name for serverless mode. Some criteria for app naming may include the following:
The app name should still be configurable.
Acceptance Criteria
Auto app naming is automatically disabled in serverless mode. In addition, there should be a default (yet overridable) app name when serverless mode is enabled.
Design Considerations
Code changes in the agent are not always necessary. One workaround that can be considered is naming the application with a lambda layer startup script but allow it to be overridable.