-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[ Chrony Receiver ] Part 1 - Adding initial component #12101
[ Chrony Receiver ] Part 1 - Adding initial component #12101
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.
Other than a couple of minor issues, this LGTM.
0c08141
to
dcdb4e9
Compare
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.
Also reviewed internally, and still LGTM, just two minor nits.
71b3829
to
0e077e4
Compare
64a0530
to
dbbc671
Compare
@jpkrohling could I get you to double check this? |
3ad75e3
to
f1b6001
Compare
Adding in the conguration of the Chrony Receiver to be added along with the metadata metric configuration.
f1b6001
to
2c9ee6c
Compare
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.
LGTM
…#34846) The README is referencing a config option as `address`, but it's actually `endpoint`. This incorrect reference was introduced in the [original PR introducing this component](open-telemetry#12101). Fixes open-telemetry#34839
Description:
Adding in the configuration of the Chrony Receiver to be added along with
the metadata metric configuration.
Link to tracking Issue:
#11789
Testing:
The default unit testing of the configuration object
Documentation:
A readme along with the generated documentation for the metdata.yml has been added.