spring-projects / spring-projects/spring-boot
Investigate how to support sending OTLP over Brave
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
There's a OtlpProtoV1Encoder in https://github.com/openzipkin-contrib/zipkin-otel and here's a sample project.
The weird situation we now have is that we use Brave as a tracer, and something OTLP-capable as a backend. But there's also Zipkin (at least the client-side components) in the mix, because it is sending the Brave Spans through the AsyncZipkinSpanHandler and the BytesMessageSender.
That means both management.zipkin.tracing.* and management.otlp.tracing.* properties could be applicable.
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 by reading OtlpProtoV1Encoder in the linked zipkin-otel project and the linked demo-zipkin-otel sample. Trace how Brave Spans move through AsyncZipkinSpanHandler and BytesMessageSender, then determine how OTLP support would interact with the management.zipkin.tracing.* and management.otlp.tracing.* properties. Done means the support approach and configuration behavior are clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100