Plugin reference

Checks for software updates on systems that use package management systems based on the apt-get(8) command found in Debian GNU/Linux and Ubuntu.
Why? Helps you keep your Debian GNU/Linuxand Ubuntu systems updated with the latest security packages.
How? By using the apt sources added to the system to see if there are any new updates to download.

Checks different AS400 system information.
Why? To help you make sure your movex system is running as it is supposed.
How? It does so by connecting to the AS400 using telnet. The plugin uses the OMS400/ODS400 commands on the target machine.

Flexible Nagios plugin for monitoring CloudWatch-enabled AWS.
Why? To monitor AWS.
How? Uses Boto3 package for interacting with AWS, and nagiosplugin library to convert the results to a Nagios-interpretable format.

Monitors BGP sessions.
Why? To identify overloaded servers.
How? Checks configured BGP peers using SNMP.

• Receive locations status.
• Send ports status.
• Messages in the group overview.

Reports the signal strength of BreezeCOM wireless equipment.
Why? To identify problems with BreezeCOM equipment related to signal strength.
How? By SNMP.

Gets various metrics from your Buildbot environment.
Why? To be able to monitor the job queues, or if you lost a connection to a build slave.
How? Query the Buildbot API for metrics.

Executes commands on remote hosts.
Why? To be able to check different statuses over an encrypted protocol.
How? The plugin uses SSH to connect to the remote host and then executes your specified check command.

Checks if the Citrix master browser returns a published application list that contains names specified in the check command.
Why? To ensure the right applications are published.
How? By communication with the Citrix server using the ICA protocol and requesting a list of published applications. It also enables you to create notifications if an application is missing from the list.

Tests clamd connections with the specified host (or Unix socket).
Why? To make sure the clam antivirus daemon is running and is responding.
How? Connects to the clam daemon either via TCP or the local Unix socket. The received string is parsed.

Monitors metrics from any instances in Amazon Web Services EC2, ELB, or RDS.
Why? To be able to keep track of how your instances are performing without installing any agents. You can check things like CPU, network, and disk.
How? This plugin reports metrics of an instance on Amazon Web Services EC2, ELB, or RDS using Amazon CloudWatch API. The Amazon credentials are read from an encrypted file. Using the Amazon CloudWatch API you can monitor the status of your instances without installing an agent or using SNMP. All you need to do is to create a read-only user, create a key pair, and add the key pair and credential keys to the OP5 Monitor server.

Amazon Web Services

Used to check a cluster of services or hosts.
Why? To make sure a clustered service is working as expected.
How? By checking defined services in OP5 Monitor.

Checks the temperature sensors of the Rittal CMC-TC monitoring system.
Why? To help you control environments where the temperature is critical.
How? By collecting data using SNMP.

Checks status of HP Insight hardware
Why? To check the status of RAID, fan, and power supplies.
How? Connects using SNMP to check values returned by Compaq Insight agents.

Checks CPU IO wait on IBM AIX.
Why? To monitor that the CPU IO wait is working as expected.
How? The CPU IO wait is calculated with help from the command iostat.

Checks the status of objects monitored by OpenManager on Dell servers using SNMP.
Why? To make sure you will be notified of hardware problems on your Dell servers.
How? Checks temperature, disks (RAID), power supply, and more using snmp.

Tests functionality of a DHCP server.
Why? To see that the DHCP server is working.
How? Requests an IP address. You can specify which IP to ask for and what server to ask.

Checks DNS servers on a specific host using dig.
Why? To verify the functionality of the DNS server.
How? By using the dig command to resolve a hostname. The plugin allows you to specify a hostname and the expected IP address.

Checks disk usage on a mounted partition.
Why? To keep track of disk usage and be notified before the disks fill up.
How? Checks disk usage on a mounted partition. Allows you to specify usage thresholds and the partitions to check.

Checks disk usage on SMB partitions.
Why? To keep track of disk usage and be notified before the disks fill up.
How? By using the smbclient program and connecting to the SMB share.

Checks DNS servers.
Why? To ensure your DNS is resolving correctly.
How? Uses the nslookup command to obtain the IP address for the given host or domain query.

Checks Docker container status.
Why? To make sure Docker containers are working as expected.
How? It uses check_docker.py and check_swarm.py to monitor Docker containers over INET or Unix sockets.

Not platform dependent

Checks the expiration date of an domain name.
The following top-level domains are supported: .com, .edu, .net, .org, .in, .co.uk, .biz, .info, .ru, .dk, .se, .fi, .ie, .us, .cn, .nu
Why? To ensure you do not miss a domain name renewal.
How? The plugin is using the whois command on a Linux system.

Checks the status of an instance on Amazon Web Services EC2.
Why? To keep track of the status of your AWS EC2 instances.
How? This plugin checks the status of an instance on Amazon Web Services EC2 using Amazon EC2 API. The Amazon credentials are read from an encrypted file. Using the Amazon EC2 API you can monitor the status of your instances without installing an agent or using SNMP. all you need to do is to create a read-only user, create a key pair, and add the key pair and credential keys to the OP5 Monitor server and you are ready to go.

Check temperature, wetness, and humidity of a probe connected to a Sensatronics EM1.
Why? To be notified when temperature, wetness, or humidity in, for example, server rooms rise above defined thresholds.
How? The plugin queries the status of Sensatronics EM1 using http protocol.

Combines several tests to create a reliable set of services that together provide the complete picture of a Microsoft exchange server's status.
Why? To verify end-to-end functionality of a complex email system.
How? By checking the must important services and performance counters.

Checks status of a web server
Why? To get the status of your web servers.
How? This plugin enables you to check a lot of different things on a web server, including response time, HTTP, HTTPS, specific URLs, match strings on a page, different ports, validity of SSL certificates, and more. You can also use it to validate certificates on mail servers.

Checking to see if there is an IRCd running and see how many users it has.
Why? To see the status of an IRC server.
How? By connecting to the IRC server and checking for a correct response. You can also set thresholds on response time.

Checks an HTTP server for JSON attributes.
Why? To check attributes of your JSON data on an HTTP server.
How? Connects to an HTTP server and checks for JSON attributes. Performance data is also enhanced to extract performance data compliant with Nagios and Graphite standards. One attribute is selected for threshold check, multiple others can be added for extracting performance data.

Not platform dependent

Support for monitoring Kubernetes clusters.
Why? To make sure Kubernetes clusters are working as expected.
How? Gets conditions and other health data over HTTP.

Not platform dependent

Checks the status of predefined filters in op5-logserver versions greater than 2.1.
Why? To check the status of a filter.
How? This plugin is run remotely on the log server using NRPE. You can specify thresholds for the number of rows that can be returned by a filter.

Checks Microsoft SQL servers.
Why? To check the status of Microsoft SQL servers.
How? Connects to a Microsoft SQL database and checks if it is accepting connections. Allows you to specify a database, user name, and password. It can also accept a query and thresholds for the number of rows that the query can return.

Checks the status of the Nagios process on the local machine.
Why? So you can be sure that you will be notified if there are any problems with your OP5 Monitor Nagios service.
How? Checks to make sure the Nagios status log is no older than the number of minutes specified by the expires option. It also checks the process table for a process matching the command argument.

Checks Check Point FireWall-1 status and policy state (must be installed).
Can check the following:

• Installed policy name; you must provide the exact name of the policy.
• Connections; you must provide warning and maximum levels.

Checks the interface state of a VRRP cluster.
Why? To ensure your VRRP interfaces are in the right state, have the right number of members in the cluster, and that the load is not too high.
How? By SNMP. Depending on the state you use as an option (master or backup), the script retrieves all the VRRP enabled interfaces and checks they are in that state. If not, it returns a critical status. By default, it checks Nokia IP platforms using VRRP.

Used to make complex web queries.
Why? You can use it to test login forms and other functions on a web site.
How? Sends a post or get request and analyses the result. A long chain of tests can be made and used for monitoring.