Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Option 1 - Using NMIS built-in Escalation and Notification

opHA provides multi-server polling with a central dashboard provided by the Master. It does NOT handle the escalation of real time events of slavesthe pollers. Escalations are handled on each Slave Poller server; emails, etc are sent from the slavepoller. For more information on configuring escalation: NMIS8 Configuration

Option 2 - Using opEvents to Monitor the opHA

...

Poller

The typical solution here is to have the slave poller send NMIS events using syslog to the master which are stored in slave_event.log, then opEvents processes this event log instead of the local event.log and opEvents on a single server can handle the events for all slavespollers.  The nodes from the remote slaves pollers will need to be added to opEvents so it knows what to do with them.

With opEvents, any event can be handled from any source, and include escalations, etc.   (opEvents running on a Master will carry out all actions as the master not as the slavepoller)

Step 1 - Enable opHA Master to receive syslogs
a. Open /etc/rsyslog.conf
b. Verify you have these modules

...

c. We need to add a section to tell the NMIS master to receive the event log form the slave poller and where to store it. Under this section add:

...