open-telemetry / open-telemetry/opentelemetry-ruby
OTLP Exporter: allow json export
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 606
- Forks
- 301
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 42
Description
Telemetry data is sent via HTTP POST request. The body of the POST request is a payload either in binary-encoded Protobuf format or in JSON-encoded Protobuf format.
Java implementation: https://github.com/open-telemetry/opentelemetry-java/blob/main/exporters/common/src/main/java/io/opentelemetry/exporter/internal/http/HttpExporterBuilder.java#L172
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
Read the OTLP Specification 1.7.0 section linked in the issue, then compare the Java reference at exporters/common/src/main/java/io/opentelemetry/exporter/internal/http/HttpExporterBuilder.java. Locate the Ruby OTLP exporter entry point and its tests; done means the exporter can send JSON-encoded Protobuf payloads as an alternative to binary encoding.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100