open-telemetry / open-telemetry/opentelemetry-cpp
Move ElasticSearch exporter from opentelelemetry-cpp to opentelemetry-cpp-contrib
Open
Nobody has claimed this yet.
do-not-stale
good first issue
help wanted
issue:blocking
- Dominant language
- C++
- Stars
- 1.4k
- Forks
- 632
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 75
Description
As per the specs only Zipkin, OTLP and Jaeger exporter belong to core repo. Rest of the exporters should be contributed to contrib repo.
Accordingly, ElasticSearch exporter should be moved to opentelemetry-cpp-contrib repo.
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 exporter placement guidance in the linked OpenTelemetry specification and inspect the exporters directory in opentelemetry-cpp-contrib. Compare that structure with the Elasticsearch exporter in opentelemetry-cpp; done means the exporter has been moved to the contrib repository and no longer belongs in core.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, elasticsearch
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100