Introduction

NMIS can be used to monitor many services, including the services that it depends on itself. This can be useful in root cause analysis if NMIS has problems.

opHA Standard

When running multiple servers utilizing opHA common pratice is to have MAIN Primary monitor all the pollers and itself. If available it is also recommend to have a primary "watch the watcher", i.e. monitor the Main Primary and the pollers as well.

Accessing the Services List

Log into your NMIS GUI and navigate to the node you’re interested in.  At the top of the node, click “service list”.

This will bring up a list of the services that particular node is monitoring.

Configuring NMIS to monitor a service

Step 1

Log into your NMIS GUI and click System, System Configuration, NMIS Nodes (devices)

Step 2

Scroll down the list and find the node you wish to monitor services on.  Click “edit” in the actions column.

Step 3

Scroll down in the box that pops up until you reach the Services section and select the services you wish to begin monitoring.  Note that you can select multiple services by holding control (for PC/Linux) or command (Mac).

Step 4

Click “Edit and Update Node”.  After the next polling cycle (usually about five minutes) you should see that the new services are being monitored.

Services Required for NMIS Modules

NMIS

NMIS requires the following services to run:

• snmpd
• mongod
• omkd
• nmisd
• httpd
• crond

OpCharts

OpCharts requires the same services as NMIS, plus

• opchartsd

OpEvents

OpEvents requires the same services as NMIS, plus:

• opeventsd

OpConfig

OpConfig requires the same services as NMIS, plus:

• opconfigd

OpFlow

OpFlow requires the same services as NMIS, plus:

• opflod