Opsview Architecture

Opsview is designed to be scalable, extensible and easy to use. Thousands of hosts can be monitored from a single Opsview server, multiple Opsview servers can be integrated into a single distributed environment. The modular and Open Source nature of Opsview facilitates customisation and integration with other systems.

Nagios monitoring engine

At the heart of Opsview is Nagios. It provides the core monitoring engine and elements of the monitoring user interface.

Web Framework - Catalyst

Catalyst is a web framework used for the Opsview user interface. It allows rapid development of new UI elements and incorporates important functionality such as authentication and database abstraction.

Relational Database - MySQL

Three databases are used within Opsview

  • Opsview: used for all configuration data
  • Runtime: contains runtime data relating to hosts and service states, using NDOUtils
  • Data warehouse: persistant storage of event and performance data. Utilised by Opsview Reports

Opsview Middleware

Application software that integrates software components that comprise Opsview. Key tasks performed by middleware application include:

  • Communication between software components
  • Generation of configuration data for each software component
  • Management of slave servers when using distributed monitoring - clustering and load balancing

SNMP Rules Engine

SNMP traps are accepted by Net-SNMP's snmptrap daemon and then passed to the rules engine. The rules engine processes incoming traps and identifies matches against pre-defined rules. Events generated by the SNMP rules engine are associated with the relevant service check and passed to Nagios.