-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Added segment synthesizer and provided ability to convert http client otel spans to external http trace segments #2745
Conversation
…client otel spans to external http trace segments
c18d106
to
e81adc9
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## next #2745 +/- ##
==========================================
- Coverage 97.30% 88.93% -8.38%
==========================================
Files 296 294 -2
Lines 46662 46486 -176
==========================================
- Hits 45404 41341 -4063
- Misses 1258 5145 +3887
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
…client otel spans to external http trace segments (#2745)
…client otel spans to external http trace segments (#2745)
…client otel spans to external http trace segments (#2745)
…client otel spans to external http trace segments (#2745)
…client otel spans to external http trace segments (#2745)
…client otel spans to external http trace segments (#2745)
…client otel spans to external http trace segments (#2745)
…client otel spans to external http trace segments (#2745)
…client otel spans to external http trace segments (#2745)
…client otel spans to external http trace segments (#2745)
…client otel spans to external http trace segments (#2745)
Description
This PR adds new keys to the rules.json(for now) to identity which type of segment should be created. I didn't enumerate all the types just yet. The intention is this will be called on the
onEnterSpan
section of the otel tracer. Maybe we bind the relevant timeslice metric recorder but for now that's for a different story(#2654)Related Issues
Closes #2648