Difference between revisions of "ZenPack:NTP Monitor"

From Zenoss Wiki
Jump to: navigation, search
(10 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{ZenPack
 
{{ZenPack
|Summary=The NTPMonitor ZenPack uses the check_ntp_peer Nagios Plugin to check the offset with the sync peer. This plugin will not check the clock offset between the local host and NTP server.
+
|Summary=This ZenPack monitors the offset between system time and a target NTP (Network Time Server) server's time.
 
|Organization=Zenoss, Inc.
 
|Organization=Zenoss, Inc.
|License=GNU General Public License, Version 2
 
 
|ZenPack name=ZenPacks.zenoss.NtpMonitor
 
|ZenPack name=ZenPacks.zenoss.NtpMonitor
 +
|Homepage=https://github.com/zenoss/ZenPacks.zenoss.NtpMonitor
 +
|Documentation URL=http://community.zenoss.org/docs/DOC-3469
 
|Source URI=https://github.com/zenoss/ZenPacks.zenoss.NtpMonitor.git
 
|Source URI=https://github.com/zenoss/ZenPacks.zenoss.NtpMonitor.git
|Flavor=free
+
|Releases=
|Releases={{Release
+
|Version=2.2.2
+
|Tag=2.2.2
+
|Release date=2015/12/08
+
|Summary=Changed check_ntp_time back to check_ntp_peer
+
|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
+
}}{{Release
+
|Version=2.2.1
+
|Tag=2.2.1
+
|Release date=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
+
}}
+
 
|Devices=
 
|Devices=
|Applications={{Application
+
|Applications=
|Product Name=NTP
+
}}
+
 
|Integrations=
 
|Integrations=
 
|DataAudits=
 
|DataAudits=
 
|Binaries=
 
|Binaries=
 +
|Flavor=core
 
}}
 
}}
This ZenPack checks the health of an NTP server and monitors the offset with the sync peer. The ZenPack uses the pre-installed Nagios plugin "check_ntp_peer" to perform this task.  
+
The <span class="zenpack">ZenPacks.zenoss.NtpMonitor</span> ZenPack monitors the difference between the system time a server is using and the time a Network Time Protocol (NTP) server is reporting.
 +
 
 +
 
 +
== Prerequisites ==
 +
 
 +
 
 +
{| class="wikitable"
 +
!width="50%"|Prerequisite
 +
!width="50%"|Restriction
 +
|-
 +
|Product
 +
|<span class="ph">Zenoss platform</span> 4.x, Zenoss 2.2 or higher
 +
|-
 +
|Required ZenPacks
 +
|ZenPacks.zenoss.NtpMonitor
 +
|}
 +
 
 +
 
 +
== Enable Monitoring ==
  
== Usage ==
 
  
 
The NTPMonitor template must be bound to the device class or device you want to monitor.
 
The NTPMonitor template must be bound to the device class or device you want to monitor.
  
# Select Infrastructure from the navigation bar.
+
<ol>
# Click the device name in the device list.
+
<li>Select Infrastructure from the navigation bar.
# Expand Monitoring Templates, and then select Device from the left panel.
+
</li>
# Select Bind Templates from the Action menu.appears.
+
<li>Click the device name in the device list.
# Add the NTPMonitor template to the list of selected templates, and then click Submit.
+
 
 +
The device overview page appears.
 +
</li>
 +
<li>Expand Monitoring Templates, and then select Device from the left panel.
 +
</li>
 +
<li>Select Bind Templates from the Action menu.
 +
 
 +
The Bind Templates dialog appears.
 +
</li>
 +
<li>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 NTP server metrics from this device.
 +
</li></ol>
 +
 
  
The NTPMonitor template is added to the list of monitoring templates.
+
== Daemons ==
== Tips ==
+
  
  
# If Error = "NTP CRITICAL: No response from NTP server"; verify if server is a NTP server
+
{| class="wikitable"
# If Error = "CRITICAL - Socket timeout after 10 seconds"; check device restrictions in ntp configuration file (/etc/ntp.conf for Linux) for "noquery".
+
!width="50%"|Type
# If Error = "NTP CRITICAL: Server not synchronized, Offset unknown"; synchronize NTP server with NTP.
+
!width="50%"|Name
 +
|-
 +
|Performance Collector
 +
|zencommand
 +
|}
 
{{ZenPackFooter}}
 
{{ZenPackFooter}}

Revision as of 16:38, 20 March 2014

Note: This is a Core ZenPack which can be found in the Core Zenoss RPM, and is fully documented in the Zenoss Extended Monitoring Guide. If you did not install this pack when you installed Zenoss Core, it can be found in $ZENHOME/packs.

Organization
Zenoss, Inc.
ZenPack name
ZenPacks.zenoss.NtpMonitor
More Information
GitHub page/HomePage
Link to more docs
View Documentation
Git sources (for cloning)
Link


Applications Monitored: 



NTP Monitor ZenPack

This ZenPack monitors the offset between system time and a target NTP (Network Time Server) server's time.

Warning

The ZenPack Catalog has moved to its new home at https://www.zenoss.com/product/zenpacks as of January 17, 2017. The following information may be out of date, and this page will eventually be removed.

Support

This ZenPack is part of Zenoss Core. Open Source users receive community support for this ZenPack via our online forums. Enterprise support for this ZenPack is provided to Zenoss customers with an active subscription.

Background

The ZenPacks.zenoss.NtpMonitor ZenPack monitors the difference between the system time a server is using and the time a Network Time Protocol (NTP) server is reporting.


Prerequisites

Prerequisite Restriction
Product Zenoss platform 4.x, Zenoss 2.2 or higher
Required ZenPacks ZenPacks.zenoss.NtpMonitor


Enable Monitoring

The NTPMonitor template must be bound to the device class or device you want to monitor.

  1. Select Infrastructure from the navigation bar.
  2. Click the device name in the device list. The device overview page appears.
  3. Expand Monitoring Templates, and then select Device from the left panel.
  4. Select Bind Templates from the Action menu. The Bind Templates dialog appears.
  5. 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 NTP server metrics from this device.


Daemons

Type Name
Performance Collector zencommand

Installation

Normal Installation (packaged egg)

  1. Download the appropriate egg file for the version of Zenoss you are running.
  2. Ensure you are logged in as the zenoss user:
    $ sudo su - zenoss
  3. Install the ZenPack:
    $ zenpack --install ZenPacks.zenoss.NtpMonitor-*.egg
  4. Restart these services:
    $ zenoss restart

Developer Mode Installation

In order to do a development mode installation you will want to clone the existing git repository, and then use the --link flag with the zenpack command:

  1. Ensure you are logged in as the zenoss user:
    $ sudo su - zenoss
  2. Start by cloning the upstream repository:
    $ git clone https://github.com/zenoss/ZenPacks.zenoss.NtpMonitor.git
  3. Next, perform the installation:
    $ zenpack --link --install ZenPacks.zenoss.NtpMonitor
  4. Finally, restart these serivices:
    $ zenoss restart

Discuss

Purplemarker.png New: Don't forget to add yourself to the Zenoss User Map!

blog comments powered by Disqus