Network Time Protocol (NTP) Offset Issues

If you have noticed any of the following issues, they may be related to the NTP offset on the hosts that are reporting metrics through the Agent:

To check the NTP offset for a host, you can run the Agent info command, using the instructions appropriate for your OS, and look for the Clocks section:

  Clocks
  ======
    NTP offset: -0.0036 s
    System UTC time: 2015-02-12 22:10:49.524660

Any significant offset can have undesired effects, and we recommend keeping hosts in sync with NTP to ensure this does not cause issues, to help we also offer an NTP Integration.

Syncing a System Clock with NTP

Instructions for syncing the system clock with NTP vary based on the operating system being used. Here are some helpful links for different operating systems.

Prevent and check NTP issues 

To prevent NTP issues, you can leverage our monitor for NTP offset to alert you when there is drift on a host.

 

Also, you can check over all the reporting hosts, the one that have offset issues.

To do so, use our Check Summary page, Inspect the check ntp.in_sync and you'll see a list of the hosts that have NTP issues.

Also note that outgoing UDP traffic over the port 123 should be allowed so the agent can confirm that the local server time is reasonably accurate according the datadog NTP servers.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk