The Network Time Protocol (NTP) integration is enabled by default and reports the time offset from an ntp server every 15 minutes. When the local agent’s time is more than 15 seconds off from the Datadog service and the other hosts that you are monitoring, you may experience:
Default NTP servers reached:
The NTP check is included in the Datadog Agent package, so you don’t need to install anything else on your servers.
The Agent enables the NTP check by default, but if you want to configure the check yourself, edit the file
ntp.d/conf.yaml in the
conf.d/ folder at the root of your Agent’s configuration directory. See the sample ntp.d/conf.yaml for all available configuration options:
init_config: instances: - offset_threshold: 60 # seconds difference between local clock and NTP server when ntp.in_sync service check becomes CRITICAL; default is 60 # host: pool.ntp.org # set to use an NTP server of your choosing # port: 1234 # set along with host # version: 3 # to use a specific NTP version # timeout: 5 # seconds to wait for a response from the NTP server; default is 1
host(Optional) - Host name of alternate ntp server, for example
port(Optional) - What port to use
version(Optional) - ntp version
timeout(Optional) - Response timeout
Restart the Agent to effect any configuration changes.
Run the Agent’s
status subcommand and look for
ntp under the Checks section.
|The time difference between the local clock and the NTP reference clock.
shown as second
The NTP check does not include any events.
Returns CRITICAL if the NTP offset is greater than the threshold specified in
ntp.yaml, otherwise OK.
Need help? Contact Datadog support.
Mistake in the docs? Feel free to contribute!