Nagios is an extensively used and very configurable open source application that monitors systems, networks and infrastructure. We have integrated with a 3rd party REST API to be able to pull data from Nagios and apply the service status and Nagios alarms onto the relevant Hyperglance entities. Nagios comes pre-bundled with the Hyperglance Appliance. 


Features

  • Alarms and service status mapped onto Hyperglance topology
  • Nagios actions, including:
    • Scheduling and cancelling planned downtime
    • Enabling and disabling notifications
    • Acknowledging problems
  • Automatically configure Nagios to monitor nodes as Hyperglance discovers them using hg2nagios.



Configure Nagios


1. You will need to configure Nagios to monitor hosts that Hyperglance is also monitoring.



2. If you are hosting Nagios yourself then you will need to install a 3rd party REST API so that Hyperglance can communicate with Nagios.
If you are using the pre-bundled installation of Nagios that comes with the Hyperglance Appliance then this API has already been installed for you.



Activate the Integration


In the Hyperglance Admin Panel  https://IP_address:8443/#/admin, select the 'Nagios' Collector under the 'Collectors' section. Click on 'Add Record' button which brings up a pop up with the necessary fields (shown below).


Note: Hyperglance Admin Panel is visible only to admin users of Hyperglance.


To use the Nagios installation that is bundled with the appliance then use the following details:

1.Nagios IP: 127.0.0.1

2.Nagios Port: 8090




Using Nagios in the Hyperglance UI


Selecting a node that is monitored by Nagios will enable you to see:


  • Nagios service status information on the attributes panel
  • Nagios alerts on the alarms panel
  • Nagios management actions under the actions button.



This information, alert-data and actions are only available on nodes that are monitored by Nagios.



Nagios Actions



  • Acknowledge Problem -  This method acknowledges a Nagios reported problem on a host or service
    • Host/Service - If selected (and available), points this action on a specific service and/or base Host
    • Comment - Comment associated to the acknowledgement
    • Author - The author of the acknowledgement
    • Persistent - Determines if this acknowledgement's comment will stay on the host or service after the problem has been resolved
    • Sticky - When true, this acknowledgement stays until the host enters an OK state. If false, the acknowledgement clears on ANY state change
  • Cancel Downtime -  This method is used to cancel previously scheduled downtimes, if any exist, and can be used on hosts and services
    • Host/Service - If selected (and available), points this action on a specific service and/or base Host
  • Disable Notifications - This method disables alert notifications on a host or service
    • Host/Service - If selected (and available), points this action on a specific service and/or base Host
  • Enable Notifications - This method enables alert notifications on a host or service
    • Host/Service - If selected (and available), points this action on a specific service and/or base Host
  • Schedule Downtime - This action is used for creating fixed length downtimes, and can be used on hosts and services
    • Host/Service - If selected (and available), points this action on a specific service and/or base Host
    • Duration - The duration, in seconds, of the downtime. Must be a value between 60 seconds and a week
    • Author -  The author of the downtime
    • Comment - Comment associated to the downtime
  • Remove Acknowledgement -  This method removes a previously created acknowledgement of an issue, if any is available, on a host or service.
    • Host/Service - If selected (and available), points this action on a specific service and/or base Host