The NTPMonitor ZenPack checks the offset of a local / internal NTP server against it's sync peer (usually a public NTP server on the internet) to ensure that syncing is working properly and that the NTP server is healthy.
This ZenPack will NOT monitor the offset between the clocks on monitored hosts and the NTP servers that they are using to sync their clocks. It is NOT intended to detect time drift on monitored hosts.
This ZenPack is only intended to be used to monitor NTP servers.
An NTP server process must be running on the host that you apply the NTPMonitor template to.
Git Sources (For Cloning)
This is an Open Source ZenPack developed by Zenoss, Inc. Enterprise support for this ZenPack is available to commercial customers with an active subscription.
- Released on 2018/05/18
- Compatible with Zenoss 5.x and 6.x
- Released on 2015/12/08
- Compatible with Zenoss Core 2.5.x, Zenoss Core 3.1.x, Zenoss Core 3.2.x, Zenoss Core 4.2.x, Zenoss Core 5.0.x, Zenoss Resource Manager 4.1.x, Zenoss Resource Manager 4.2.x, Zenoss Resource Manager 5.0.x
- Released on 2015/02/03
- Compatible with Zenoss Core 2.5.x, Zenoss Core 3.1.x, Zenoss Core 3.2.x, Zenoss Core 4.2.x, Zenoss Resource Manager 4.1.x, Zenoss Resource Manager 4.2.x
- Zenoss 5.0+
The NTPMonitor template must be bound to the device class or device you want to monitor.
- Select Infrastructure from the navigation bar.
- Click the device name in the device list.
- Expand Monitoring Templates, and then select Device from the left panel.
- Select Bind Templates from the Action menu.appears.
- Add the NTPMonitor template to the list of selected templates, and then click Submit.
The NTPMonitor template is added to the list of monitoring templates. You can now start collecting the clock offset between the NTP server and it's sync peer.
- No longer relies on Nagios plugins to monitor NTP servers
- Added unit tests
- Rewritten as a PythonCollector's PythonDataSource
- Now uses yaml definition (ZenPackLib) instead of objects.xml
- Added IPv6 support
- Tested with Zenoss Resource Manager 5.3.3, 6.1.2 and 6.2.0
- Switched from check_ntp_peer to check_ntp_offset. (ZEN-15833)
- Switched back to check_ntp_peer (ZEN-15833)
- Tested for compatibility on Zenoss 5.0.9