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:
To install the check on the agent:
/opt/datadog-agent/embedded/bin/pip install .
Create a dedicated virtualenv and follow the instructions in this paragraph to work with the check.
To install the check in dev mode:
pip install -e .[dev]
To run the tests:
python setup.py test
Once installed, the check is available as:
To build the wheel package:
python setup.py bdist_wheel
The Agent enables the NTP check by default, but if you want to configure the check yourself, create a file
ntp.yaml in the Agent’s
conf.d directory. See the sample ntp.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(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
info subcommand and look for
ntp under the Checks section:
Checks ====== [...] ntp ------- - instance #0 [OK] - Collected 1 metrics, 0 events & 0 service checks [...]
The NTP check is compatible with all major platforms.
|The time difference between the local clock and the NTP reference clock.|
shown as second
The NTP check does not include any event at this time.
Returns CRITICAL if the NTP offset is greater than the threshold specified in
ntp.yaml, otherwise OK.
Need help? Contact Datadog Support.
Learn more about infrastructure monitoring and all our integrations on our blog