[Feature]: Upgrade to OTEL Collector 1.37 #7400
Conversation
Signed-off-by: Harshil Gupta <harshilgupta1808@gmail.com>
Signed-off-by: Harshil Gupta <harshilgupta1808@gmail.com>
c1c8286 to
139d50a
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7400 +/- ##
=======================================
Coverage 96.44% 96.44%
=======================================
Files 375 375
Lines 22951 22951
=======================================
Hits 22135 22135
Misses 617 617
Partials 199 199
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
5a31590 to
ee43963
Compare
| { | ||
| "kind": 2, | ||
| "name": "foobar", | ||
| "parentSpanId": "", |
There was a problem hiding this comment.
Unexpected, what is changed upstream to cause this?
There was a problem hiding this comment.
Yeah, it made me curious as well. Though I'm not versed with opentelemetry-collector repo, using claude I was probably able to identify the root cause. Lemme know if it makes sense:
- This adds a marshal template which omits the field if its equal to the default.
Resovles to:
if ms.orig.ParentSpanId != data.SpanID([8]byte{}) {
dest.WriteObjectField("parentSpanId")
ms.orig.ParentSpanId.MarshalJSONStream(dest)
}
ParentSpanIdis not being set in the test thus it gets the default value of SpanID, i.e.data.SpanID([8]byte{})
There was a problem hiding this comment.
cool, thanks for finding the reference (open-telemetry/opentelemetry-collector#13450). It's not a deal-breaker change, but I commented on that PR because they were saying "no changes to marshaling".
|
Please change pr title to be about OTEL upgrade |
|
Thanks! |
Fixes #7398
Description of the changes
REGENERATE_SNAPSHOTS=true make testto update snapshotsHow was this change tested?
Checklist
jaeger:make lint testjaeger-ui:npm run lintandnpm run test