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
[Tracing] Skeleton for alternative opentelemetry collector. #11092
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #11092 +/- ##
==========================================
- Coverage 71.10% 71.10% -0.01%
==========================================
Files 763 766 +3
Lines 153166 153153 -13
Branches 153166 153153 -13
==========================================
- Hits 108906 108893 -13
+ Misses 39828 39826 -2
- Partials 4432 4434 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
approving to unblock.
|
||
pub struct Collector {} | ||
|
||
impl Collector { |
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.
can you add some comment about context, eg. how/where this will be used?
@@ -0,0 +1,20 @@ | |||
[package] | |||
name = "near-tracing" |
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.
We already got o11y, is there a good reason to introduce a separate crate if o11y would end up depending on this anyway?
(not that it matters much either way...)
This can function as an alternative collector that neard can send tracing spans to. It works. We just need to figure out how to store this data next.