...

...

Service Polling

Polling for Service monitoring was already variable, and is configured when defining the service parameters in Services.nmis, and by enabling the sample cron entry in /etc/cron.d/nmis, the default is for 3 minutes, this can be as low as every minute.  Uncomment the line in the cron and change the */3 to be */1 or at the minimum required frequency.

# ######################################################
# Optionally run a more frequent Services-only Collection
# */3 * * * *  /usr/local/nmis8/bin/nmis.pl type=services mthread=true

Defaults

Polling Interval Defaults.  (If no policy is assigned.)

...

Configuration

Configure a Polling Policy

...

From the 'Polling Policy' drop down menu the previously configured polling policies will be available for assignment.  Once finished click the 'Edit and Update Node' button at the bottom of the Edit Node window.

Verification

This step is optional, if you need to show and see the verification that the activities are happening with higher or lower frequency.  Also watching the RRD graphs in NMIS and zooming in will show this well.

SNMP/WMI

In order to verify that the polling interval is occurring at the dictated frequency we can run a query against an applicable rrd file.  Likely candidate rrd files for each type of polling are listed below.

• SNMP -    /usr/local/nmis8/database/nodes/<node name>/interface/<interface name>.rrd
• WMI -   / /usr/local/nmis8/database/nodes/<node name>/health/WindowsProcessor.rrd

...

The number to the far left is the Unix epoch timestamp that the sample was collected.  Subtracting the time stamps between subsequent samples will provide the polling interval in seconds.

ICMP/Ping

In order to verity verify the ICMP/Ping polling frequency we can use tcpdump to observe how often echo requests are being send to the subject node. 

...