Use aws resource detector in ruby layer

Open
  • Is something wrong?
#2,740 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
aws, ruby
Domain
observability

Research direction

Start by locating the Ruby layer’s code that injects Lambda information into OpenTelemetry environment variables, then check how the AWS resource detector is used in the repository. Update the layer to use the detector and remove that injection. Done when the detector supplies the Lambda resource information and the environment variables are no longer injected.

Written by the indexing model from the issue text.

Description

enhancement ruby

Is your feature request related to a problem? Please describe.
Currently the ruby lambda is injecting the lambda info into otel environment variables rather than using the aws detector.

Describe the solution you'd like

The layer uses the aws resource detector & removes the environment variable injection.

Describe alternatives you've considered
N/a

Additional context
N/a

Tip: React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.

Dominant language
Go
Stars
433
Forks
249
Avg merge
1d 12h
Merged PRs (30d)
39

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from open-telemetry/opentelemetry-lambda

All issues in open-telemetry/opentelemetry-lambda

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.