Replace instrumentation-all with explicit dependencies
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 64/100
Research direction
Start by locating the Ruby layer’s dependency manifest and identifying where it declares instrumentation-all. Check which instrumentation packages it currently brings in and which need to remain disabled. Replace the aggregate dependency with direct dependencies for the included packages, omitting those that should stay disabled; done when the Ruby layer builds with the intended set.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Currently the ruby layer is using instrumentation-all which is bringing in a number of un-necessary instrumentation packages & in some cases some of them need to be disabled.
Describe the solution you'd like
The instrumentation-all dependency is removed & instead replaced with direct dependencies on all instrumentation included within the all. Any instrumentation which needs to be disabled should be left out.
Describe alternatives you've considered
Leave it as is
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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from open-telemetry/opentelemetry-lambda
-
processor/cold_start
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
open-telemetry/opentelemetry-lambda#2738 ·
Maintainers usually reply within 2 days
-
Fix install-toolsOpengo
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
open-telemetry/opentelemetry-lambda#2736 ·
Maintainers usually reply within 2 days
-
enhancement javascript
Difficulty 5/5 Over a week Newbie friendliness 35/100
open-telemetry/opentelemetry-lambda#2744 ·
Maintainers usually reply within 2 days
-
enhancement python
Difficulty 3/5 1-2 days Newbie friendliness 55/100
open-telemetry/opentelemetry-lambda#2742 ·
Maintainers usually reply within 2 days
-
enhancement ruby
Difficulty 3/5 1-2 days Newbie friendliness 65/100
open-telemetry/opentelemetry-lambda#2740 ·
Maintainers usually reply within 2 days
All issues in open-telemetry/opentelemetry-lambda
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
php/frankenphp#2829 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
teradata-labs/loom#624 ·
Maintainers usually reply within 1 day