open-telemetry / open-telemetry/opentelemetry-cpp
Observing performance issue for opentelemetry 1.17.0
Open
Nobody has claimed this yet.
triage/needs-information
- Dominant language
- C++
- Stars
- 1.4k
- Forks
- 632
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 75
Description
We have instrumented component with Opentelemetry 1.17.0 APIs for metrics with OTLP exporter & observing performance issue.
We need to check how we can benchmark these numbers?
Is there any way we can improve performance like java has RESUABLE_DATA option?
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
No files, tests, or entry points are identified. Start by locating the metrics SDK and OTLP exporter benchmarks for the 1.17.0 APIs, then compare allocation and export costs with the reported Java reusable-data behavior; done means documented benchmark results and a clearly scoped performance change or explanation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- observability-sre, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100