Page tree
Skip to end of metadata
Go to start of metadata

Who watches the watcher?  It is important when using a monitoring/management system that you know it is operational, with some level of beneficial recursion, NMIS supports many techniques for managing servers and applications.  You should ensure that something in your environment is watching NMIS.

Related Content

Table of Contents


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. Common services to monitor for opmantek servers are listed below, for up to date Service.nmis file you can go to  The team updated these services in the last 12 months to cover using HTTPS or HTTP and updated service process checks.

The current services shipping with NMIS9 at this time are:

  • NMIS9 Workers
  • NMIS9 Scheduler
  • MongoDB
  • Opmantek Web Daemon
  • "OMK Stack HTTP" or "OMK Stack HTTPS"
  • SSL Expiry Check
  • opEvents Daemon
  • opConfig Daemon
  • opCharts Daemon

Also, it is good to monitor:

  • crond
  • syslog
  • ssh

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 requires the following services to run:

  • snmpd
  • mongod
  • omkd
  • nmisd
  • httpd or apache (or nginx)
  • crond


OpCharts requires the same services as NMIS, plus

  • opchartsd


OpEvents requires the same services as NMIS, plus:

  • opeventsd


OpConfig requires the same services as NMIS, plus:

  • opconfigd


OpFlow requires the same services as NMIS, plus:

  • opflowd

  • No labels