[receiver/ntp] use a Weaver model #41999
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dcf5186 to
568efe3
Compare
ArthurSens
reviewed
Aug 14, 2025
There was a problem hiding this comment.
I had a similar problem that I've commented here #40698 (comment) when trying this out.
Not sure if I'm doing something wrong or if the schema is incorrect 🤔
ArthurSens
reviewed
Aug 14, 2025
ArthurSens
approved these changes
Aug 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Move NTP receiver to use a weaver model to power the generation of its metadata.yaml.
This is related to the work taking place with open-telemetry/semantic-conventions#2544
Note this starts the work of generalizing Weaver access across multiple receivers.