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.
**Describe the bug** The release notes for v0.1.0 of the [nodejs lambda layer](https://github.com/open-telemetry/opentelemetry-lambda/releases/tag/layer-nodejs%2F0.1.0) are wrong -- they appear to reference the Python lambda layer instead 
**Describe the bug** onboard [auto-instrumentations-node](https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/metapackages/auto-instrumentations-node) instead of managing a library instrumentation list in https://github.com/open-telemetry/opentelemetry-lambda/blob/main/nodejs/packages/layer/src/wrapper.ts Refer to python wrapper improvement https://github.com/open-telemetry/opentelemetry-lambda/pull/164 **Steps to reproduce** If possible, provide a recipe for reproducing...
Currently `OPENTELEMETRY_COLLECTOR_CONFIG_FILE` is a environment variable used to set the config file from any of the config map providers such as [http, s3, yaml.](https://github.com/open-telemetry/opentelemetry-lambda/blob/main/collector/internal/collector/collector.go#L60) etc., as per the naming convention...
Consider adding changelog linking for various new sdk, agent, instrumentation version changes etc. per the sig discussion. Simplify how to find changes in community assets.
As part of new releases we'll need to create changelogs to track versioning
Separate the instrumentation from the existing layer and provide a standalone Collector layer
Separate the instrumentation from the existing layer and provide a standalone Collector layer
Separate the instrumentation from the existing layer and provide a standalone Collector layer
Separate the instrumentation from the existing layer and provide a standalone instrumentation layer
Separate the instrumentation from the existing layer and provide a standalone instrumentation layer