-
Notifications
You must be signed in to change notification settings - Fork 35
Closed
Description
The AWS Lambda extension currently gathers traces and Lambda metrics. This issue is about extending the current extension to also support collecting log events out of the box.
The Lambda runtime provides the Lambda function / application logs through the Lambda Logs API directly to the extension. Currently the extension subscribes to the Logs API to retrieve platform
type logs for collecting metrics.
To also collect application logs, the extension needs to also subscribe to function
type logs:
- Receive the logs through the Lambda Logs API
- Enrich the logs with meta information (e.g.
faas.*
fields,cloud.*
fields, etc.) - Send the logs to the APM server's new logs intake (Add Logs Intake API (POC) apm-server#8757)
Scope
- The collected lambda logs should be available in the APM UI's logs tab for the APM service that represents the Lambda function.
- The logs are enriched with meta information.
- Preliminary performance tests show that the tradeoff between shipping the logs directly through the extension and the implied latency overhead is reasonable.
This can be treated as a meta
issue and be split up into further implementation tasks if necessary.