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:
By default, the check will detect which cloud provider the agent is running on and use the private NTP server of that cloud provider if available. If no cloud provider is detected, the agent will default to the NTP servers below:
0.datadog.pool.ntp.org1.datadog.pool.ntp.org2.datadog.pool.ntp.org3.datadog.pool.ntp.orgThe 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.
Note: If you edit the Datadog-NTP check configuration file, restart the Agent to effect any configuration changes.
Run the Agent’s status subcommand and look for ntp under the Checks section.
| ntp.offset (gauge) | The time difference between the local clock and the NTP reference clock. Shown as second |
The NTP check does not include any events.
ntp.in_sync
Returns CRITICAL if the host clock is more than the configured threshold away from the NTP time. Returns UNKNOWN if the Agent can not connect to the NTP server. Returns OK otherwise.
Statuses: ok, critical, unknown
Need help? Contact Datadog support.