Monitoring Microsoft clustered servers requires some extra configuration. This how-to describes how to configure op5 Monitor to monitor drives and win32-services on clustered Windows servers.
This howto describes how to recive SNMP-Traps with op5 Monitor.
This document covers the upgrade paths for op5 products such as op5 Monitor, op5 System, op5 Logserver Extension and op5 Statistics Extension.
Dell server hardware can be remotely monitored via SNMP. The plugin used here comes with the op5 Monitor plugin package as default. To be able to monitor your Dell server you need to have the following installed on the monitored server: Dell openmanage Server Administrator" (Managed Node), a.k.a 'OMSA' >= 5.1.0
HP printers with JetDirect-cards can be monitored using one of two plugins. This article describes both approaches. The status information required is the printers global status.
This howto will describe how you use Event Handlers with op5 Monitor to let monitor take action upon an event, for an example restart a service on a certain state-change.
In this How-To we will be using a small perl script that uses the op5 Monitor plugin called check_http to graph the response time of a webserver. All commands in this How-To are executed in an ssh connection at the op5 Statistics server.
This how-to describes how to setup your op5 Monitor server with Oracle Instant Client to be able to use check_oracle directly towards the Oracle Database without the need of 3rd party agents.
For the purpose of rapid recovery, op5-backup has been written. It creates a tarball archive of all data relevant to the installed op5 products so they in case of disaster can be quickly restored using op5restore.sh. The script can be used to either store the backed up data locally, on a NFS/CIFS share to later be protected by an enterprise backup system, or sent over FTP to a remote host for safekeeping. The strategy to use will of course depend on your current backup environment and policies, but the tarball produced must be protected by some kind of additional backup method so it can be retrieved during a total harddrive failure.
op5 Monitor is shipped with many plugins that cover most monitoring needs. But what to do if one of your corporate applications can not be monitored straight out of the box? Often you can find a plugin at www.nagiosexchange.org, and since op5 Monitor and Nagios uses the same plugin format you can often simply download a plugin, put it in /opt/plugins/custom/ and start using it.
However, if you can not find a suitable plugin anywhere you might have to write your own plugin. Since the plugin interface is very straight-forward, anyone with a fair amount of UNIX scripting experience can do this. This article aims to describe the format and walk you through writing a simple plugin. It is intended for the op5 system administrator who wants to extend the capabilities of an op5 System and leave the boss impressed with how precise data can be extracted.
The purpose of this article is describing how op5 Monitor can be used to monitor these core features of an Active Directory and make sure that notifications are sent about common errors.
You can use op5 Monitor to query op5 LogServer on how many matches a filter return and then throw OK|WARNNG|CRITICAL values depending on the information returned. You can also get a url in your Monitor window that points to the op5 LogServer with the current filter checked.
Any monitoring system, including op5 Monitor, needs to be adjusted to suit your organizations specific needs. This how-to describes the basics of identifying the source(s) of your notifications and adjusting thresholds and configuration to get rid of false/uninteresting or exaggerated alerts ("alarms"/notifications). A new installation definitely needs tuning, but it's also a good idea to generate reports on a regular basis to prevent being flooded with notifications
op5, the op5 logo, and op5 graphics are the servicemarks, trademarks, or registered trademarks owned by op5 AB.
Sitemap | Terms and Conditions | Privacy Policy | Trademark | Phone +46 (0) 8-58 83 01 00
How to monitor your application server with op5 Monitor and JMX4Perl
In this how-to we will cover how to monitor your application server via JMX with op5 Monitor with the plugin check_jmx4perl and the agent jolokia. We will also have a glance at monitoring application servers trough a JMX-proxy for agentless monitoring where agents are not possible to use.