open-telemetry / open-telemetry/opentelemetry-cpp-contrib
HTTP or GRPC in config
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 153
- Forks
- 184
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 26
Description
Describe your environment
I am compiling from the source
Should I compile two different versions, on with gRPC and another with HTTP?
-DWITH_OTLP_GRPC=ON
-DWITH_OTLP_HTTP=ON
In case of compile with gRPC and HTTP = ON, how could I select which to use? or it is not necessary to?
What is the expected behavior?
A selector of which protocol use
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 source file or test is named. Start by tracing the CMake options -DWITH_OTLP_GRPC and -DWITH_OTLP_HTTP and the OTLP exporter configuration to determine how protocol selection currently works. Done means documenting or implementing an unambiguous way to select HTTP or gRPC when both options are enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc
- Domain
- api, build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100