open-telemetry / open-telemetry/opentelemetry-lambda
Respect OTLP Exporter environment when configuring exporters
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 432
- Forks
- 246
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 47
Description
Is your feature request related to a problem? Please describe.
I made the assumption I could change the exporter config on the NodeJS Lambda layer by setting OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf, however it appears to be hard-coded in the NodeJS Lambda layer to http/json.
Describe the solution you'd like
When using the NodeSDK directly it allows you to configure the exporters from the environment. Naturally, it feels like you should be able to configure the NodeJS OpenTelemetry Lambda layer using similar environment.
The solution I'd propose is respecting the similar environment variables, so that using the NodeJS Lambda layer behaves similarly to using the Node SDK.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the NodeJS Lambda layer's exporter configuration and compare it with the Node SDK's “Configure exporters from environment” guidance linked in the issue. Check how OTEL_EXPORTER_OTLP_PROTOCOL and related environment variables are handled. Done means the Lambda layer respects the environment configuration and supports the requested http/protobuf behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, node.js
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100