💤 Swap Zipkin server for Zipkin Receiver from OTel Collector Contrib#5045
💤 Swap Zipkin server for Zipkin Receiver from OTel Collector Contrib#5045yurishkuro merged 15 commits intojaegertracing:mainfrom
Conversation
Signed-off-by: Yuri Shkuro <github@ysh.us>
Signed-off-by: Yuri Shkuro <github@ysh.us>
Signed-off-by: Yuri Shkuro <github@ysh.us>
Signed-off-by: Yuri Shkuro <github@ysh.us>
Signed-off-by: Yuri Shkuro <github@ysh.us>
Signed-off-by: Yuri Shkuro <github@ysh.us>
Signed-off-by: Yuri Shkuro <github@ysh.us>
| @@ -0,0 +1,79 @@ | |||
| [ | |||
There was a problem hiding this comment.
I used the existing zipkin_v1_merged_spans.json file (Zipkin JSON v1), converged into object model, and re-serialized as JSON. It uses different representations for many fields, like raw numbers instead of hex strings for IDs.
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #5045 +/- ##
==========================================
- Coverage 95.58% 95.55% -0.04%
==========================================
Files 319 313 -6
Lines 18794 18161 -633
==========================================
- Hits 17965 17353 -612
+ Misses 665 647 -18
+ Partials 164 161 -3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Signed-off-by: Yuri Shkuro <github@ysh.us>
| "spans": [ | ||
| { | ||
| "trace_id": "AAAAAAAAAAI=", | ||
| "trace_id":"QoVouqoJRn5CjmiKqglGfw==", |
There was a problem hiding this comment.
(breaking 🛑) had to change this because of the error TraceID: has length 8 yet wanted length 16. Jaeger receiver did not have such limitation.
Signed-off-by: Yuri Shkuro <github@ysh.us>
| // limitations under the License. | ||
|
|
||
| package server | ||
| package handler |
There was a problem hiding this comment.
This was testing exhaustively TLS settings on Zipkin endpoint, so I decided to keep it, just move from a different location. It works against the Zipkin receiver now.
Signed-off-by: Yuri Shkuro <github@ysh.us>
jkowall
left a comment
There was a problem hiding this comment.
lgtm. One potential issue is keeping this sync with the upstream Otel changes. I do not think this will happen much with Zipkin being stagnant but it's a potential point of additional work.
|
What sync are you referring to? Basically my plan is to only use OTEL's implementation going forward and if any issues direct them upstream. We still support Zipkin Thrift in the agent, which is a separate implementation, but we should be able to remove it once we sunset the agent. |
Which problem is this PR solving?
Description of the changes
TraceID: has length 8 yet wanted length 16. Jaeger receiver did not have such limitation.--collector.zipkin.keep-alivesetting is not supported in the OTEL receivergo mod tidyremoved allgo-openapidependencies and a few othersHow was this change tested?
cmd/collector/app/handler/zipkin_receiver_test.gothat submit various Zipkin formats to the receiverChecklist
jaeger:make lint testjaeger-ui:yarn lintandyarn test