-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
New component: NTP receiver #34375
Comments
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
I am happy to sponsor this. |
#### Description Introduce a new receiver, NTP receiver. This is the first PR as skeleton for the receiver. #### Link to tracking issue Related to #34375 #### Testing N/A #### Documentation metadata.yaml, README.
Saw this got released in 0.112.0. We use OTP MFA, so clock sync is important to us. So just tried to use it with the example configuration here: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/ntpreceiver/README.md , but getting this error when validating the config and trying to restart the collector:
Any ideas? |
It's not shipping in contrib yet. See open-telemetry/opentelemetry-collector-releases#723 |
Marking this issue as closed as the receiver has landed. |
The purpose and use-cases of the new component
This receiver retrieves clock offset from ntp server, respecting the TOS https://www.pool.ntp.org/tos.html.
It emits one metric, the offset in seconds from the NTP server.
Example configuration for the component
Telemetry data types supported
metrics
Is this a vendor-specific component?
Code Owner(s)
atoulme
Sponsor (optional)
@MovieStoreGuy
Additional context
No response
The text was updated successfully, but these errors were encountered: