Exporter naming consistency
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reading the exporter implementations and package definitions to compare their current names with the proposed exporter-{{protocol}}-{{variant?}}-{{signal?}} pattern. The issue does not name specific files or tests, so first locate the exporters and metapackages; done means their naming and bundle relationships follow the proposal, including the stated variant and signal rules.
Written by the indexing model from the issue text.
Description
Naming of exporters are currently inconsistent. Proposing to standardise implementations into “exporter-{{protocol}}-{{variant?}}-{{signal?}}” with variant being grpc, http, file. Variant & signal only apply when the exporter supports multiple.
Metapackages can bundle everything ie exporter-otlp contains http, grpc & eventually file exporters, exporter-otlp-trace contains exporter-otlp-http-trace etc.
- Dominant language
- Ruby
- Stars
- 613
- Forks
- 306
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 21
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a 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-ruby
-
enhancement metrics spec-compliance spec:development stale
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
open-telemetry/opentelemetry-ruby#2369 · 2 comments ·
Maintainers usually reply within 2 days
-
Make instrument name conflict detection case-insensitivePossibly taken @naveedsajjdawan claimed this 41 days ago. Openbug good first issue metrics spec-compliance spec:stable stale
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
open-telemetry/opentelemetry-ruby#2357 · 2 comments · 1 assignee ·
Maintainers usually reply within 2 days
-
keep metrics
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-telemetry/opentelemetry-ruby#2129 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 57/100
open-telemetry/opentelemetry-ruby#2497 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
open-telemetry/opentelemetry-ruby#2437 · 2 comments ·
Maintainers usually reply within 2 days
All issues in open-telemetry/opentelemetry-ruby
Similar issues
-
🐛 bug 👩💻 équipe CE 🧑🏭 entreprises
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
betagouv/conseillers-entreprises#4808 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
yosiat/panko_serializer#250 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
cline/mcp-marketplace#3886 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100