opentelemetry-lambda
opentelemetry-lambda copied to clipboard
Create your own Lambda Layer in each OTel language using this starter code. Add the Lambda Layer to your Lamdba Function to get tracing with OpenTelemetry.
As part of the WG effort, there's a need to review the current state of the world for function as a service https://docs.google.com/spreadsheets/d/14IeGuQRJlAg9YxjKun__VowzOXRxUKyjFFfrV2XnkBI/edit#gid=0
To track sig items we should use a project board with the various tasks and owners. https://github.com/open-telemetry/opentelemetry-lambda/projects?query=is%3Aopen
**Describe the bug** Logging exporter v0.68 started to merge separate lines into one line with "\n" separator. AWS CloudWatch messages for v0.66: _2023-01-06T15:33:00.412Z info TracesExporter {"kind": "exporter", "data_type": "traces", "name":...
Currently the code owners for the repo are @Aneurysm9 @codeboten @wangzlei @NathanielRN, is this still accurate?
Please remove the direct console.log or use the Logging system which can be configured to omit certain log levels. ``` console.log('Registering OpenTelemetry'); ```
This would be similar to what exists in the collector repository: https://github.com/open-telemetry/opentelemetry-collector/blob/main/.github/workflows/check-links.yaml
Java lambda layer relies on joda, but we are not including it as dependency in the wrapper or agent
**Describe the bug** The request handler for the java layer-wrapper uses joda: https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/instrumentation/aws-lambda/aws-lambda-events-2.2/library/src/main/java/io/opentelemetry/instrumentation/awslambdaevents/v2_2/TracingRequestWrapperBase.java#L33 However joda is not being added as runtime dependency of our lambda layer. We did not notice...
### Issue Building the layer with `./python/build.sh` does not result in the same layer as the one published [here](https://aws-otel.github.io/docs/getting-started/lambda/lambda-python). I would like to build my own layer (with adot) so...
The NodeJS layer currently uses `@opentelemetry/instrumentation-redis` that only supports Node-Redis 2 and 3.[^0][^1] Please consider adding `@opentelemetry/instrumentation-redis-4`[^2] to the set of available instrumentations. Based on what `@opentelemetry/auto-instrumentations-node`[^3] does I believe...