open-telemetry / open-telemetry/opentelemetry-ruby
OTLP Profile exporter
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 606
- Forks
- 301
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 42
Description
The default URL path for requests that carry profiling data is /v1development/profiles and the request body is a Protobuf-encoded ExportProfilesServiceRequest message.
Java implementation: https://github.com/open-telemetry/opentelemetry-java/tree/main/exporters/otlp/profiles/src/main/java/io/opentelemetry/exporter/otlp/profiles
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 OTLP Specification 1.7.0 section linked in the issue and compare the Java implementation in exporters/otlp/profiles. Identify the corresponding Ruby OTLP exporter entry points and existing exporter tests, then verify that profile data is sent to /v1development/profiles as an ExportProfilesServiceRequest.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100