Use node-sdk package for layer
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- node.js
- Domain
- backend
Research direction
Start by locating the Node.js layer implementation and the node-sdk package it proposes to use; the issue does not name specific files or tests. Compare how the current custom code creates and manages the SDK with the package’s capabilities, and assess the performance impact. Done means the layer uses node-sdk to create and manage the SDK without a noticeable performance change.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
I want to reduce maintenance effort of the nodejs layer by using the node-sdk library to create & manage the sdk rather than a custom solution.
Describe the solution you'd like
Sdk is created via Node-sdk and custom implementation. The change should not have a noticeable impact on performance.
Describe alternatives you've considered
N/a
Additional context
This will help to resolve nodejs issues and ensure the sme's are maintaining it.
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
-
enhancement ruby
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
open-telemetry/opentelemetry-lambda#2741 ·
Maintainers usually reply within 2 days
-
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 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