http://docs.opsview.org/ 2010-09-09T12:16:31+01:00 http://docs.opsview.org/ http://docs.opsview.org/lib/images/favicon.ico text/html 2009-06-11T10:15:07+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:access&rev=1244711707&do=diff There are 4 levels of access: * View - the ability to see status * Notification - the ability to receive notifications * Action - the ability to schedule downtime or acknowledge a problem (used to be known as change) * Admin - the ability to change configurations text/html 2009-03-20T12:01:52+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:acknowledgements&rev=1237550512&do=diff Acknowledgements are a way of disabling notifications for a host/service. It allows the user to put a comment to show the current situation for that object. This is a way of handling “unplanned outages”. If requested, an acknowledgement notification will be sent to all the contacts that get failure notifications. text/html 2009-03-03T15:45:40+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:advancedapache&rev=1236095140&do=diff There are some advanced options available for the Opsview front end. Opsview via HTTP over SSL By default Opsview is accessed by unencrypted HTTP. To use the more secure HTTP over SSL (HTTPS) communication you must first set up your certificates in your web server (not detailed here) and also amend the /usr/local/nagios/etc/opsview.conf file to include text/html 2009-05-21T10:34:25+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:agents&rev=1242898465&do=diff Opsview supports the use of monitoring agents to gather data from remote devices. The most common types of monitoring agents used with Opsview are SNMP (Simple Network Management Protocol) and NRPE (Nagios Remote Plugin Executor). Generic Agents SNMP SNMP agents are provided with all managed network devices such as switches, routers and firewalls. SNMP polling is the standard method for gathering data, monitoring plugins exist for all commonly used devices. text/html 2009-06-30T13:44:34+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:alpha&rev=1246365874&do=diff Firstly, do NOT use this in production. Secondly, only use this on a test system. We realise this is the same as the first point, but it is worth repeating. :) The alpha release is your chance to get the latest development copy of Opsview 3 and try it out. These instructions will tell you how to obtain and how to setup a system based on your existing configuration. Depending on your environment, you could have both Opsview systems monitoring the same hosts. text/html 2009-04-06T09:29:44+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:api&rev=1239006584&do=diff Opsview has an API which allows you to create/delete hosts and take actions in the status views such as enable/disable notifications at a hostgroup level, as well as getting status information for services and hostgroups. There are 3 ways to access the APIs: text/html 2010-06-28T12:24:04+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:architecture&rev=1277724244&do=diff Opsview is 3 tiered system. * Web front end * Application server * Datastores [Architecture] Web front end This is a very thin layer provided by Apache. This just serves static files and proxies dynamic requests to the application server. text/html 2010-06-28T12:24:04+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:audible_alerts&rev=1277724244&do=diff Opsview can generate audible alerts on the nagios cgi pages, such as status.cgi and tac.cgi, but not currently in any of the hostgroup hierarchy pages (this is on our wishlist waiting for a sponsor). To enable audible alerts add the following line to the opsview.conf file within /usr/local/nagios/etc/ text/html 2009-07-13T13:53:52+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:backups&rev=1247489632&do=diff Opsview nightly backups A cronjob for the nagios user will be present on the master server called rc.opsview cron_daily. This runs daily housekeeping tasks, including the backing up of various parts of Opsview. The scope of this backup is to save configuration and files so that you can restore a working Opsview server quickly. text/html 2009-06-30T13:52:41+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:beta&rev=1246366361&do=diff Firstly, do NOT use this in production. The beta release is your chance to get the latest development copy of Opsview 3 and try it out. These instructions will tell you how to obtain and how to setup a system based on your existing configuration. Depending on your environment, you could have both Opsview systems monitoring the same hosts. text/html 2008-12-18T12:10:14+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:beta_testing&rev=1229602214&do=diff This page describes how to test the Opsview 3 beta release (due end of December). Warning: This beta is not ready for upgrading your existing systems - please wait for the official Opsview 3 release. The basic process is: * install Opsview 3 on a separate server * copy existing data (including configuration, runtime, ODW and RRD data) to the new server * Run migration scripts text/html 2009-09-29T09:55:33+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:centos-installation&rev=1254214533&do=diff Supported CentOS version is 4.5 and 5.3 There is a perl performance issue on RHEL5/CentOS5 with perl 5.8.8 Please see the following links: * <https://bugzilla.redhat.com/show_bug.cgi?id=196836> (Fedora reference) * <https://bugzilla.redhat.com/show_bug.cgi?id=379791> (RHEL5 reference) text/html 2009-06-30T14:05:39+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:changes&rev=1246367139&do=diff The major changes between 2.14 and 3: * Opsview now uses Nagios 3 * Data stored in all databases uses UTC timezone, rather than the server's timezone * Nagios status tables now in innoDB format * Opsview Web can be relocateable * 10% speed improvements in config generation * New performance graphing framework * RRDs upgraded to new format to fix long metric names * Using Service Groups for categorization of Service Checks * New default configuration * New viewports summary … text/html 2009-05-06T15:14:34+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:contact&rev=1241619274&do=diff This page defines the contacts, or the users, of Opsview. Be aware that some changes are immediately applicable: * password changes (though your session is still intact) * contact deletion means the user will not be able to use Opsview straight away * in Opsview 3.1, some access rights do not require a reload text/html 2009-05-13T09:42:02+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:customising&rev=1242204122&do=diff Status screens The status screens under /status and /viewports use the latest CSS techniques to separate presentation from the status information. You can override the base CSS by updating the file /usr/local/nagios/share/stylesheets/custom.css. This file will not be changed on an upgrade. text/html 2009-03-09T16:37:41+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:dbs-on-diff-server&rev=1236616661&do=diff This document details how to set up Opsview to use databases on a different database server, rather than running the database on the Opsview master server. There will be an outage to the Opsview server during the backup and the restore. The majority of the time will be in the restore of the ODW database server - we recommend you perform a test restore to get timings before you follow this process on your production system. text/html 2009-06-03T13:21:09+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:debian-agent&rev=1244031669&do=diff This page is not yet complete but should be done during the 3.1 development cycle. This page details how to build the Debian and Ubuntu agents and assumes some basic understanding on compilation on these platforms. From the source repository Prerequisites Basic Steps The follow these steps: text/html 2009-06-16T11:21:28+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:debian-installation&rev=1245147688&do=diff For supported Debian releases please refer to platforms. Debian Installation For a fresh Debian install we recommend using 'netinst' image then using aptitude to install SSH Daemon. Other required packages will be installed as part of Opsview installation. text/html 2008-12-20T13:00:33+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:designing-system&rev=1229778033&do=diff Scalability Considerations Variables affecting how many devices can be monitored * Number of service checks per host * Median interval for service checks * Type of checks being executed (quality of plugin code, local execution vs agent queries, etc) * Network latency * Stability of system being monitored (number of host / service state changes per minute) text/html 2009-03-23T11:45:06+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:downtime&rev=1237808706&do=diff Downtimes allow you to set hostgroups, hosts or services that will be expected to fail. This is useful for “planned outages”, such as an engineer visit, or a software upgrade. The main difference is that the checks will continue to be run, but notifications will not be sent out. text/html 2009-05-29T13:45:43+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:embeddedservice&rev=1243601143&do=diff These are services that are automatically generated by Opsview. They are usually services that there are multiple versions of. There are 3 types of embedded checks: * SNMP Interfaces - for the selected interfaces on the host edit page under the SNMP tab * Slave node - for checks of slave connectivity from the Opsview master * Cluster node - for clustered slaves, to check the ssh connectivity between each other and handle failover text/html 2010-06-28T12:24:04+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:exceptions&rev=1277724244&do=diff It is possible at the host or the host template selection screen for services to monitor to make an exception for the arguments passed to the plugin. The initial use case was for check_load, where a different load average was desired for different hosts. text/html 2009-05-07T12:35:40+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:fastcgi&rev=1241696140&do=diff FastCGI/Lighttpd is an extra set of daemons that sit between the Opsview web application and the Apache web server. Instead of one Opsview backend server, several are started and load is shared between them. This helps to prevent Opsview being locked by a long running process or database query. text/html 2010-06-28T12:24:04+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:graph&rev=1277724244&do=diff This page provides a summary of the options Host Title This is the name of the host as it appears in the host list page. By starting to type, a slect of host names will be presented for easier selection. Service The service name to graph from the host. This will be updated to show only those services on the given host with information available to graph. text/html 2009-05-08T16:26:18+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:graphoptions&rev=1241796378&do=diff When viewing graphs, there is an options tab on the right hand side: When clicked, the tab drawer will open out: If you click the Options link, it will take you to the full set of options: By default, the URL /rrdgraph is public. You can change this setting in System Preferences. If it is not public, then you will to authenticate before being able to view the graph, and authentication is based on the authorisation rules. text/html 2009-05-29T15:06:12+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:hamaster-debian-howto&rev=1243605972&do=diff Configuration is based on Linux-HA software More information: <http://www.linux-ha.org/> Author: Philipp Noack Note: If you clone the first server after setup you will NOT get it running. The second server has to be installed exactly like the first one! text/html 2009-05-29T15:12:30+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:hamaster&rev=1243606350&do=diff This document covers the theory on setting up high availability for the Opsview master. There are different ways of achieving high availability. You could run the Opsview master in a virtual machine and provide availability at the virtual machine level - that setup is outside of the scope of this document. text/html 2009-01-27T14:44:59+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:help&rev=1233067499&do=diff Opsview Web Application Errors Validation Errors Validation errors occur in the Opsview user interface when characters are entered that are not permitted. These should be detected as you complete the field, however Opsview also performs validation within web application framework. Sometime it is the web application that detects the problem and it will generate an exception error. text/html 2009-07-24T10:11:10+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:host&rev=1248426670&do=diff This page allows you to configure hosts. From Opsview 3.1 onwards, you need to have the CONFIGUREHOSTS access level in your role to be able to configure hosts. Hostname or IP This is the primary hostname, or IP, for this host. Bear in mind that a host does not have to be an actual host, so this field does not have to be an actual hostname or IP. text/html 2009-04-21T15:37:49+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:host_groups_hierarchy&rev=1240324669&do=diff From this page, you can define the hierarchy of the hostgroups. The principle is that a hostgroup contains all the enclosing hostgroups. You can drag and drop the hostgroups to define the hierarchy. You will need to reload for the hierarchical changes to take effect in the Hostgroup Hierarchy status pages. text/html 2010-06-28T12:24:04+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:hosticons&rev=1277724244&do=diff From Opsview 2.14.1 there is a script to allow for adding and removing host icons. The icons themselves must be 40×40 and in GIF format. The command has documentation within it (use hosticon_admin --help). Adding new host icons Ensure the following packages are installed: text/html 2009-03-20T13:47:16+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:hosttemplate&rev=1237556836&do=diff Host templates contain a list of service checks. If a host has this host template associated with it, then it will inherit all the service checks from the host template. Host templates are used to group common services together for association with a host. text/html 2010-06-28T12:24:04+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:i18n&rev=1277724244&do=diff There is basic support for internationalisation (or i18n) in Opsview from 2.7.1. This will be expanded over time. We use the Catalyst I18N plugin, which depends on the Locale::Maketext::Simple module, which is based on gettext. We're just building on the shoulders of giants. text/html 2009-09-01T13:32:21+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:importantconcepts&rev=1251808341&do=diff This page describes the important concepts of how Opsview, using Nagios, monitors your environment. Host and Services A service is a check of some sort. A service is the most granular thing in Nagios (a service can either be active or passive, but we assume active for the moment). text/html 2010-06-28T12:24:04+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:knownissues&rev=1277724244&do=diff This page is deprecated. See faq text/html 2010-04-09T13:07:15+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:ldap&rev=1270814835&do=diff If you want to authenticate users in Opsview from LDAP or Active Directory, there are two parts to it: * Users can authenticate to Opsview using their LDAP credentials * Optionally, you can run a synchronisation script to create users in Opsview based on LDAP group membership. This also controls authorisation text/html 2009-04-06T15:24:37+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:managementui&rev=1239027877&do=diff Configuration * Host options * Contact options * Service Check options * Host Template options Advanced * SNMP Interface Polling * Slave Node Checks * Cluster Node Checks * Roles * System Preferences Other * Exceptions and Timed Exceptions * Event Handlers text/html 2009-01-27T11:33:23+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:massacknowledgements&rev=1233056003&do=diff See Mass acknowledgements on this page. text/html 2010-06-28T12:24:04+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:migrating&rev=1277724244&do=diff For those users that have a working Nagios system and wish to migrate to Opsview, there is a tool available within the distribution to aid the move. NOTE: The tool is work in progress and does not migrate all configuration at the moment, but gives a helping hand in the initial stages. text/html 2009-03-12T13:30:40+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:migratinghardware&rev=1236864640&do=diff This document is for migrating Opsview from one hardware to another. You will effectively have two different instances of Opsview, each with their own data stores. Note: If you have a distributed environment, you should disable slaves on the old Opsview, otherwise there will be contention between the two masters. text/html 2009-03-27T10:14:45+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:monitoringui&rev=1238148885&do=diff Status bar The status bar along the bottom has status lights for Server Status and Configuration Status. On certain pages, it also has a counter which tells you when the next refresh of the page will be. You can click on the Refresh text to force an immediate refresh. text/html 2009-05-21T17:17:52+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:mysql&rev=1242922672&do=diff Use MySQL client to execute SQL statements Common Tasks Backing up Opsview databases and configuration * Edit etc/opsview.conf to set correct backup destination su - nagios /usr/local/nagios/bin/rc.opsview backup Backing up Opsview database only * Ensure opsview.conf is correct text/html 2009-03-23T14:34:35+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:nagiosplugins&rev=1237818875&do=diff It should be possible to use any Nagios plugin with Opsview. Plugins API A plugin runs and returns 3 things: * a status code (0 = OK, 1 = WARNING, 2 = CRITICAL, 3 = UNKNOWN) * a single line of output (Opsview 3 allows multiple lines) * optionally, some performance data text/html 2010-06-28T12:24:04+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:nagiospluginsalerts&rev=1277724244&do=diff This information has been moved to here: <http://docs.opsview.org/doku.php?id=opsview3:faq:usage#nagios_plugin_alerts> text/html 2009-03-10T09:31:11+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:nagvis&rev=1236677471&do=diff Nagvis is a 3rd party component that allows graphical representations of the status of Opsview services. Note: Time representations in Nagvis will be in UTC, due to changes to the Runtime database in Opsview 3. The URL path /nagvis can be used to access Nagvis. More information in: text/html 2009-01-15T11:59:03+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:nmis&rev=1232020743&do=diff NMIS, or Network Management Information System, is a project which provides detailed traffic information about routers, switches and servers, via SNMP. Limitations While NMIS does a lot of other functions similar to the rest of Opsview, only the parts that are specifically for interface collection and display are integrated into Opsview. text/html 2009-04-17T15:23:35+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:notificationmethods&rev=1239978215&do=diff You can define custom SMS notification methods. Opsview is shipped with two by default: * AQL - where you can send SMS alerts via AQL's web site * SMS4NMS - where you can send alerts via locally attached GSM modems You can add your own notification methods here. However, only one can be active at any time. You choose the one that is active in the /admin/systempreference System Preference screen, then all contacts will use this notification method using the Mobile field in the edit contact… text/html 2009-08-24T19:39:47+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:odw&rev=1251139187&do=diff The Opsview Data Warehouse, or ODW, is the long term storage for monitoring data. It converts the data from the Runtime database into an OLAP datawarehouse format. A core requirement for a datawarehouse is to not normalise the data too much, yet still allow queries to be easily created. As you'll see, hopefully we will have reached this target. text/html 2009-02-05T13:17:51+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:opsview-reports&rev=1233839871&do=diff These are PDF reports which are generated using data from the ODW database. You can configure information about the report from the Opsview web application and run an adhoc report. Adhoc reports are always the current report to date, so if the report run is a monthly report, it will be run for the current month - obviously it will be incomplete. text/html 2010-06-28T12:24:04+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:opsviewconfigfiles&rev=1277724244&do=diff Most configuration is performed via Web User Interface however some system options are located in configuration files. opsview.conf This is the main configuration file for Opsview, it can be found in /usr/local/nagios/etc. Make your local changes to this file. text/html 2010-06-28T12:24:04+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:opsviewplugins&rev=1277724244&do=diff It is possible to extend the functionality of Opsview via plugins. There are various hooks in the code which allows calling of external functions. There are two forms of plugins: scripts and perl classes. Scripts Where the current functionality is provided via scripts, external scripts can be called to run other tasks. For install, at the process_configs stage, after the Nagios configuration has been loaded, any other scripts in /usr/local/nagios/opsview-plugins/process_configs/* will be execu… text/html 2009-09-11T09:41:15+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:opsviewshutdown&rev=1252658475&do=diff There are two services on an Opsview master server: * opsview - which runs the background daemons for monitoring, including an agent on the master * opsview-web - which runs the application server to serve the web pages If you run these commands as the nagios user, make sure you use su - nagios (with the dash) to switch to the nagios user as you will need the environment variables to be setup. text/html 2009-04-23T15:23:21+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:osx-agent&rev=1240496601&do=diff This page details how to build the Mac OS X agent and assumes some basic understanding on compilation on a Mac. Prerequisites * PackageMaker - installed as part of Xcode developer tools (located in: /Developer/Applications/Utilities) * subversion * make, gcc and other compiler tools text/html 2009-07-28T13:00:31+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:platforms&rev=1248782431&do=diff By saying 'supported' we mean that assistance may be provided for issues encountered with software or hardware listed since we have carried out some level of testing. We cannot guarantee that no issues will be encountered. Supported Operating Systems Note: For all platforms, we build against the latest updates (including major fixes and security updates) on the respective operating systems. Therefore, we suggest your target platform also has the latest updates. text/html 2009-04-27T12:04:52+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:pluginoutput&rev=1240830292&do=diff Active checks are plugins which give textual output. This page will list some of the most common or cryptic ones, with suggestions for troubleshooting. Basic technique Firstly, get the actual command that is run. As an admin user, search for the host in the list pages, select the contextual menu and click the number of servicechecks. This will list all the services associated with the host and the arguments used. text/html 2009-05-06T14:04:05+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:prefork&rev=1241615045&do=diff From Opsview 3.1, Catalyst::Engine::HTTP::Prefork is a different way of starting up the Opsview Web application for improved UI response to reduce CPU load at the expense of more memory. We recommend you have at least 1 GB memory on the Opsview Master server when using HTTP::Prefork. text/html 2009-03-24T09:18:48+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:prereqs&rev=1237886328&do=diff This page describes some prerequisites that should be followed before installation of the Opsview software. Note that package installation of Opsview will bring in other dependencies. However, some of the tasks below may require the dependent software to be installed first. This will be noted. text/html 2009-03-24T09:08:30+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:quickstart&rev=1237885710&do=diff This document will introduce you to using Opsview. Prerequisites * Opsview software installed * A web browser * A host in your network to monitor We assume your Opsview server is at <http://opsviewserver> Login Goto <http://opsviewserver>. This will bring up the login screen. The default user is: text/html 2010-06-28T12:24:04+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:report&rev=1277724244&do=diff Reports are consist of a report type and a selection. There are some customisations that are possible based on the report type. Report type At the moment, there is only one report type: Monthly availability by hostgroup This field is not changeable once the report has been created. text/html 2009-05-05T10:34:10+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:rhel-agent&rev=1241516050&do=diff This page details how to build the RHEL and CentOS agents and assumes some basic understanding on compilation on these platforms. Prerequisites * rpmbuild package Note: the rpmbuild process will state further prerequisite rpm's to install. Basic Steps You can optionally set the environment variable 'distrib' to be appropriate for the platform, i.e.: text/html 2009-09-29T09:54:54+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:rhel-installation&rev=1254214494&do=diff For supported Red Hat Enterprise Linux releases please refer to platforms. There is a perl performance issue on RHEL5/CentOS5 with perl 5.8.8 Please see the following links: * <https://bugzilla.redhat.com/show_bug.cgi?id=196836> (Fedora reference) * <https://bugzilla.redhat.com/show_bug.cgi?id=379791> (RHEL5 reference) text/html 2009-05-06T15:05:33+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:role&rev=1241618733&do=diff From Opsview 3.1, you can customise the roles available in Opsview for assigning to contacts. List view [Role List page] The default list of roles covers the most common roles. The two roles, Public and Authenticated user, are system roles and cannot be deleted. The accesses that the Authenticated user role has will be inherited by all the other configurable roles. text/html 2009-02-03T17:02:44+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:rrdgraphing&rev=1233680564&do=diff You specify the graphs you want to draw via URL parameters. To get the RRD graph, use your browser to GET from /rrdgraph with some of the available options: ParameterDescriptionduration Defines the duration period. You can use any duration specifier RRD allows. Defaults to 1dstart Defines the start time of the graph. You can use anything that RRD allows. Defaults to end-durationend Defines the end time of the graph. Defaults to nowheight Defines height of graph in pixe… text/html 2010-06-28T12:24:04+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:selection&rev=1277724244&do=diff A selection is a set of things that can be used to run reports against. At the moment, only hostgroups are selectable. Host groups The left hand list is the list of host groups that are in this selection. To add more, enter the name of a host group on the right hand text field. It will provide a dynamic drop down list of possibilities as you type. text/html 2009-07-24T10:17:09+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:servicecheck&rev=1248427029&do=diff Service checks are the things that you care about. From the Service Check pages, you can define how to check a service, when to check it and what to do if if it fails. They are deliberately separated from hosts, so you need to associate service checks against hosts to start monitoring them. This host + a service check will be referred to as a service, in Opsview terminology. text/html 2009-04-09T08:59:34+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:sharedodw&rev=1239263974&do=diff It is possible to have multiple distinct Opsview master systems all feeding to a shared ODW instance. There are some constraints: * Each Opsview Master is separately administered and have no knowledge of each other * Each Opsview Master is on the same version (you can upgrade each master individually - see below for details) * There are no Opsview host names that are duplicated between all Opsview Masters. (Note: This is the host name, as understood by Nagios - you can have different ho… text/html 2009-05-29T14:21:41+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:slaveclusters&rev=1243603301&do=diff When configuring a slave, you can set more than one host to be in the slave cluster. This provides failover and load balancing. Each host in this cluster is called a node. Note: Within a slave cluster, there is support for a single node failure. A double node failure in the same cluster will result in active checks being missed. text/html 2009-08-25T09:39:30+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:slavesetup&rev=1251189570&do=diff Within large organisations where there are large numbers of devices to monitor or in a distributed datacenter that can span continents, countries, counties or cities, a single Opsview server can get bogged down trying to process all the necessary device checks and fall behind leading to delayed checks and notifications. text/html 2010-06-28T12:24:04+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:snmp_trap_tracing&rev=1277724244&do=diff This page allows you to define which hosts you want Opsview to start tracing traps for. Choose by hostname in the text field area (a live search will be performed) and press Add to move into the list. You have to submit the page for the hosts to have tracing enabled. Tracing will not start until a reload has occurred. text/html 2009-02-03T16:56:44+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:snmptrapconfiguration&rev=1233680204&do=diff Introduction The SNMP Trap mechanism allows devices on a network to send information back to a management host using the SNMP protocol. This is particularly useful on large networks as it can be used in place of active SNMP (where a device is polled for status information), thus reducing network load. Devices can usually be configured to send specific types of trap such as link status changes, BGP, HSRP and many others, making this a flexible monitoring option. How to configure specific dev… text/html 2009-09-17T15:08:20+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:snmptrapsetup&rev=1253196500&do=diff Overview Opsview supports SNMP Trap Processing using a perl-based rules engine, allowing you to match specific traps from devices on your network and generate appropriate alerts. In order to do this, SNMP traps must be passed from the operating system to Opsview - this page details how to set this up for Debian and RedHat GNU/Linux distributions. text/html 2009-06-16T12:18:36+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:solaris-installation&rev=1245151116&do=diff For supported Sun Solaris releases please refer to platforms. Installing on Solaris If you plan to use a fresh Solaris installation take note of the following. Partitioning One large / partition is fine, but we recommend partitioning schema of at least / and /var text/html 2009-06-30T13:31:12+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:source-installation&rev=1246365072&do=diff This information has been moved to the developer documentation. text/html 2010-06-28T12:24:04+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:stalking&rev=1277724244&do=diff This stalking option (called Log Every Message in the web interface) in the service checks edit page has been deprecated. This option forces Nagios to log an entry in the nagios.log file for every check result that comes in that is different from the current state. However, since Opsview will by default store every check resultin the runtime database, so this option places unnecessary load on the Opsview master server. text/html 2009-04-28T10:57:00+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:systempreference&rev=1240912620&do=diff Opsview webserver This is the webserver for accessing the web interface of Opsview. If this field has not been saved before, the field will be automatically populated based on the URL. At reload time, if this system preference has not been saved, Opsview will use the master server's hostname (or IP). text/html 2010-06-28T12:24:04+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:testing&rev=1277724244&do=diff In Opsview, there are 2 sets of tests run: * Automated tests * Manual Automated tests This uses perl's TAP (Test Anything Protocol) framework. To run, execute: cd opsview-core make test on a developement server. This runs a series of test scripts in t/*.t. Files that do not match this criteria are ignored. text/html 2009-07-17T11:05:32+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:ubuntu-installation&rev=1247825132&do=diff For supported Ubuntu releases please refer to platforms. Known issues Note: On Ubuntu Hardy, an issue has been raised where Opsview Web will not start up with these errors: ERROR - Errors encountered: Caught exception in Opsview::Web::Controller::Status::Service->default "DBD::mysql::st execute failed: Lost connection to MySQL server during query ERROR - Caught exception in Opsview::Web::Controller::Root->end "Can't insert new Opsview::Auditlog: DBI connect('database=opsview;host=localhost'… text/html 2009-05-01T12:30:37+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:unix_customise_agent&rev=1241177437&do=diff The Opsview unix agent package is based upon the Nagios NRPE daemon. The unix agents can be modified to add extra plugins as as below. Newer agents allow for supplementary packages to be created and installed over the top of the Opsview agent, which enables packaged customisations. text/html 2009-06-30T13:27:38+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:upgrading&rev=1246364858&do=diff This pages details the steps to perform when upgrading Opsview. Most actions are handled during the package installation, so this information details the manual pre and post upgrade tasks. Pre upgrade * Verify that the Opsview configuration is committed. As part of the upgrade, an Opsview reload will be run * Verify all the Opsview slaves are contactable - as part of the upgrade on the slaves will be pushed the new files * Run the backup script. This will backup the whole of /usr/local… text/html 2009-11-03T10:07:08+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:upgrading_from_2.14&rev=1257242828&do=diff Prerequisites You must upgrade Opsview to at least version 2.14.1 before you upgrade to Opsview 3. This release includes some changes required for a smooth upgrade to Opsview 3. Note: If you are on Opsview 2.7 or 2.8, you will need to upgrade to 2.14 first as database upgrade scripts for 2.7 and 2.8 have been removed. text/html 2010-06-28T12:24:04+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:usingeventhandlers&rev=1277724244&do=diff Event handlers are optional commands that are executed whenever a host or service state change occurs. An obvious use for event handlers (especially with services) is the ability for Opsview to proactively fix problems before anyone is notified. However, this should not be a reason to ignore root cause analysis! text/html 2010-06-28T12:24:04+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:versions&rev=1277724244&do=diff Note: This comes into effect from Opsview 2.10. Opsview version numbers will take the following format, A.B.C.D, where: * A.B = the major release number * C = the point release number * D = the SVN build number You can find the version number of your install of Opsview by looking at the version number in the side navigation at the bottom. If you click on this number, you will get the SVN build number. text/html 2009-06-02T11:05:26+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:vmware_vm&rev=1243937126&do=diff The Basics Download The Opsview VMWare Virtual Machine is intended to provide a demonstration package for easily evaluating Opsview. The image can be obtained from the Opsview download site at <http://downloads.opsview.org>. Compatibility The VM is configured for VMware Player. It may be necessary to use VMware Converter if you're planning to run this VM on VMware ESX Server. text/html 2009-03-31T10:07:35+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:webauthentication&rev=1238490455&do=diff Opsview uses mod_auth_tkt as the mechanism for granting authentication. This provides Single Sign On (SSO) functionality. If you have a valid ticket, then you should get access to the system. If you do not have a valid ticket, then Opsview will use Catalyst to handle the authentication. By default, authentication occurs based on the password stored for the contact. However, it is possible to configure Opsview to use LDAP as the authentication system. text/html 2009-01-27T14:47:09+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:webexception&rev=1233067629&do=diff If you get an error message while using Opsview please let us know the following information: * Full contents of the error message, a screen-shot is fine * URL of web page producing error * The version of Opsview you are using * The date and time of the error text/html 2009-09-14T16:25:34+01:00 http://docs.opsview.org/doku.php?id=opsview3.0:windows-agent&rev=1252941934&do=diff The Opsview Agent for Microsoft Windows uses NSClient++ which is a Nagios compatible monitoring daemon. The Agent package is created using InstallAware, a proprietary application for creating Microsoft Windows packages. It is capable of creating self extracting executables as well as full MSI packages for automated installation.