Lei Wang
Lei Wang
OpenTelemetry Lambda SIG wants to publish public [Lambda layer](https://docs.aws.amazon.com/lambda/latest/dg/configuration-layers.html) in AWS accounts for integration test, soaking and distro. Lambda users can play OTel by consuming these public Lambda layers freely...
## Background **Package Link**: https://docs.aws.amazon.com/lambda/latest/dg/golang-handler.html Support OpenTelemetry in AWS GoLang/Custom Runtime. Instrument user's handler function in AWS Lambda. Refer other language such as [Java](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/aws-lambda-1.0), Js, [Python](https://github.com/open-telemetry/opentelemetry-lambda/tree/main/python/src/otel/otel_sdk/opentelemetry/instrumentation/aws_lambda), [.Net](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Contrib.Instrumentation.AWSLambda). ## Proposed Solution...
All logs in AWS Lambda output to one CloudWatch log group, the collector extension logs will mess up with user's Lambda application logs. Collector extension should support adjust collector log...
At the moment Lambda Collector extension layer contains [very limit components](https://github.com/open-telemetry/opentelemetry-lambda/blob/main/collector/lambdacomponents/default.go#L20-L23) due to the the reason described [here](https://github.com/open-telemetry/opentelemetry-lambda/blob/main/docs/design_proposal.md#22-memory-consumption). Adding more collector components into code is cautious because we don't want...
**Is your feature request related to a problem? Please describe.** Build Collector layer based on user's config, please see details in https://github.com/open-telemetry/opentelemetry-collector-builder/issues/4 **Describe the solution you'd like** Use opentelemetry-collector-builder to...
https://github.com/open-telemetry/opentelemetry-lambda/blob/main/nodejs/sample-apps/aws-sdk/deploy/main.tf#L21-L23 does not work, the env variable config is overrided by [wrapper.js](https://github.com/open-telemetry/opentelemetry-lambda/blob/main/nodejs/packages/layer/src/wrapper.ts#L79-L81)
We need to collect lambda version number and alias information automatically as part of the trace. This help to build intelligence int the analysis and insights system to automatically detect...
Refer discussion in https://github.com/open-telemetry/opentelemetry-lambda/pull/21#discussion_r608305375 Right now Lambda collector extension has only Collect-core exporters, such as `otlpgrpcexporter`, `loggingexporter`, etc. Can we bring in popular exporters like `awsxrayexporter`, `datadogexporter`? AWS has maintained...
**Is your feature request related to a problem? Please describe.** Before [opentelemetry-lambda CNCF account ](https://github.com/open-telemetry/community/issues/685)is available, aws-observability is the only OTel Lambda layer provider. In term of meeting more user's...
**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...