-
Notifications
You must be signed in to change notification settings - Fork 33
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
Add an OTLP receiver to Weaver to prepare for the weaver registry live-check
command
#548
base: main
Are you sure you want to change the base?
Conversation
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.
clippy found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.
weaver registry live-check
command
…the server is ready or an error occurs
…e that occurs on Windows in the CI/CD pipeline.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #548 +/- ##
=====================================
Coverage 74.6% 74.6%
=====================================
Files 51 51
Lines 3965 3965
=====================================
+ Hits 2958 2959 +1
+ Misses 1007 1006 -1 ☔ View full report in Codecov by Sentry. |
…ten_otlp_requests function.
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.
Amazing! This opens up a whole load of new use cases for weaver! :)
This PR aims to facilitate the creation of commands such as validating the compliance of an OTLP stream against a semconv registry or generating a semconv registry from an OTLP stream.
Weaver is already used in the context of a CI/CD pipeline, this is simply about extending the possibilities for validation or semconv registry generation in a more live context.
An
otlp-receiver
can now easily be launched within Weaver to implement these commands or any other commands that make sense in this context. A skeleton of the commandweaver registry live-check
is provided to help future contribution.Notes:
build.rs
explaining to regenerate the vendored gRPC stubs. Most of the files presents in this PR are either proto files or code generated from those proto files.Next Step:
Someone will implement the
weaver registry live-check
command. A great example of this approach was demonstrated by @jerbly during the Semantic Convention Tooling SIG on January 15, 2025.