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.
Bumps google.golang.org/protobuf from 1.31.0 to 1.33.0. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a...
Otherwise metrics won't work
Addressing issue: https://github.com/open-telemetry/opentelemetry-lambda/issues/1196
**Is your feature request related to a problem? Please describe.** If `Config.Validate()` of a component returns false, the collector lambda layer cannot start in AWS lambda. As a result, the...
**Describe the bug** We are using AWS Java Lambda along with otel lambda ARN arn:aws:lambda:us-east-1:184161586896:layer:opentelemetry-javaagent-0_1_0:1 to auto instrument the application flow. Whenever lambda is triggered we are seeing same traceid...
**Describe the bug** When in AWS lambda using the java agent layer, both for layer v1 and v2. You can't access the Opentelemetry instance defined by the layer. `GlobalOpenTelemetry.get()` returns...
**Describe the bug** We use the Java wrapper with opentelemetry-lambda-layer.zip and the `opt/otel-handler`. The lambda is triggered via AWS event bridge whenever a new object is created in an S3...
**Describe the bug** A clear and concise description of what the bug is. Metrics is not exported. **Steps to reproduce** If possible, provide a recipe for reproducing the error. Step...
**Describe the bug** OTEL Python Layer does not always flush metrics at the end of lambda invocation. **Steps to reproduce** 1. Deploy a lambda with the following python code: handler.py...
**Describe the bug** In our application, we discovered an issue where the Node Lambda functions, which should ideally represent the root span, are being assigned a Parent ID. This issue...