Plugin reference
Overview
Listed below are all the plugins included with standard OP5 Monitor distributions.
You can extend the functionality by installing custom plugins. For more information, see Custom plugins.
Note: If you have upgraded from an earlier version of OP5 Monitor or installed custom plugins, you may have additional plugins in your OP5 Monitor instance.
check_adam
Commands | check_adam |
Description |
Used to check the status of digital input coils in the Adam environment module.
Why? To make it easy to monitor environments and other elements with your Adam module How? Everything is checked using SNMP. |
Supported platforms | Adam module |
Categories | Environmental |
Support level | Level 6 (low and best effort) |
Tags | adam, environment |
check_apica_responsetime
Commands | check_apica_responsetime, check_apica_authfile_responsetime |
Description |
Checks the response time and status of the latest check of your Apica WPM service. check_apica_responsetime will alert if the severity is not i (informational). Why? This is a way to extend your normal monitoring by having the Apica WPM service doing advanced web application monitoring for you. OP5 Monitor takes care of the notifications and includew the results from Apica in reports. How? You need an Apica account. The plugin then connects to the Apica WPM API and requests the status of your WPM check. The plugin then gets the results back in JSON format. Only the severity will trigger alerts, not the response time. The thresholds are set inside your Apica account. |
Supported platforms | Apica WPM |
Categories | Web |
Support level | Level 4 (high and fully supported) |
Tags | web, http, apica |
check_apt
Commands | check_apt |
Description |
Checks for software updates on systems that use package management systems based on the apt-get(8) command found in Debian GNU/ |
Supported platforms | Debian GNU/ | and systems
Categories | Operating systems |
Support level | Level 4 (high and fully supported) |
Tags | debian, ubuntu, system packages, apt |
check_as400
Commands | check_as400 |
Description |
Checks different AS400 system information. |
Supported platforms | AS400 |
Categories | Operating systems |
Support level | Level 6 (low and best effort) |
Tags | as400, oms400, ods400, movex |
nagios_aws
Commands | nagios_aws |
Description |
Flexible Nagios plugin for monitoring CloudWatch-enabled AWS. |
Supported platforms | Not platform dependent |
Categories | Misc, AWS |
Support level | Level 6 (low and best effort) |
Tags | aws, cloudwatch |
For guidance in using the nagios_aws
plugin, see Nagios AWS plugin.
check_bgpstate
Commands | check_bgpstate |
Description |
Monitors BGP sessions. |
Supported platforms | Not platform dependent |
Categories | Misc |
Support level | Level 5 (medium and bug support) |
Tags | network, bgp |
check_biztalk
Commands | check_biztalk_cluster_host_instance, check_biztalk_msdtc, check_biztalk_orchestration, check_biztalk_ports, check_biztalk_queues, check_biztalk_sendports, check_biztalk_specific_locations, check_biztalk_spool_size |
Description |
The plugin is used to monitor the Microsoft BizTalk application. The following can be monitored:
How? The plugin uses the BizTalk msg database for monitoring. |
Supported platforms | Microsoft BizTalk |
Categories | Misc |
Support level | Level 5 (medium and bug support) |
Tags | microsoft biztalk, database |
check_breeze
Commands | check_breeze |
Description |
Reports the signal strength of BreezeCOM wireless equipment. |
Supported platforms | BreezeCOM boxes |
Categories | Networking |
Support level | Level 5 (medium and bug support) |
Tags | breezecom, wireless, snmp |
check_buildbot
Commands | check_buildbot_jobs, check_buildbot_jobs_specific, check_buildbot_connected, check_buildbot_connected_specific |
Description |
Gets various metrics from your Buildbot environment. |
Supported platforms | Not platform dependent |
Categories | Ci |
Support level | Level 4 (high and fully supported) |
Tags | buildbot, ci, build environment |
check_by_snmp_cpu
Commands | check_by_snmp_cpu_total_usage_v2, check_by_snmp_cpu_total_usage_v3, check_by_snmp_cpu_user_v2, check_by_snmp_cpu_user_v3, check_by_snmp_cpu_nice_v2, check_by_snmp_cpu_nice_v3, check_by_snmp_cpu_system_v2, check_by_snmp_cpu_system_v3, check_by_snmp_cpu_idle_v2, check_by_snmp_cpu_idle_v3, check_by_snmp_cpu_iowait_v2, check_by_snmp_cpu_iowait_v3, check_by_snmp_cpu_steal_v2, check_by_snmp_cpu_steal_v3, check_by_snmp_cpu_custom |
Description | Checks CPU usage over SNMP. Why? To be able to monitor CPU usage on hosts where you cannot install any agents. How? Collects monitored data over SNMP. |
Supported platforms | / |
Categories | SNMP, CPU |
Support level | Level 5 (medium and bug support)
|
Tags | unix, linux, snmp, net-snmp, cpu, iowait |
check_by_snmp_disk
Commands | check_by_snmp_disk_list_available_disks_v2, check_by_snmp_disk_used_v2, check_by_snmp_disk_list_available_disks_v3, check_by_snmp_disk_used_v3, check_by_snmp_disk_custom |
Description | Checks disk information on hard drives using SNMP. Why? To be able to monitor disk usage on hosts where you cannot install any agents. How? Collects monitored data over SNMP. |
Supported platforms | / |
Categories | SNMP, file system |
Support level | Level 5 (medium and bug support) |
Tags | unix, linux, snmp, net-snmp, storage, disk, hardware |
check_by_snmp_disk_io
Commands | check_by_snmp_disk_io_list_available_disks_v2, check_by_snmp_disk_io_nread_v2, check_by_snmp_disk_io_nwritten_v2, check_by_snmp_disk_io_reads_v2, check_by_snmp_disk_io_writes_v2, check_by_snmp_disk_io_load_v2, check_by_snmp_disk_io_list_available_disks_v3, check_by_snmp_disk_io_nread_v3, check_by_snmp_disk_io_nwritten_v3, check_by_snmp_disk_io_reads_v3, check_by_snmp_disk_io_writes_v3, check_by_snmp_disk_io_load_v3, check_by_snmp_disk_io_custom |
Description | Checks disk information about IO on hard drives using SNMP. Why? To be able to monitor disk usage on hosts where you cannot install any agents. How? Collects monitored data over SNMP. |
Supported platforms | / |
Categories | SNMP, file system |
Support level | Level 5 (medium and bug support) |
Tags | unix, linux, snmp, net-snmp, disk, io, hardware |
check_by_snmp_extend
Commands | check_by_snmp_extend_v2, check_by_snmp_extend_v3, check_by_snmp_extend_custom |
Description | Runs other plugins using SNMP. Why? If you do not want to use other types of agents, this plugin lets you run plugins on remote systems with tools that are usually readily packaged by vendors. How? Collects monitored data over SNMP. |
Supported platforms | / |
Categories | SNMP |
Support level | Level 5 (medium and bug support) |
Tags | unix, linux, snmp, net-snmp, process, processes |
check_by_snmp_load_avg
Commands | check_by_snmp_load_avg_v2, check_by_snmp_load_avg_v3, check_by_snmp_load_avg_custom |
Description | Checks CPU load average over SNMP. Why? To monitor CPU load average on hosts where you cannot install any agents. How? Collects monitored data over SNMP. |
Supported platforms | / |
Categories | SNMP, CPU |
Support level | Level 5 (medium and bug support) |
Tags | unix, linux, snmp, net-snmp, cpu, load |
check_by_snmp_memory
Commands | check_by_snmp_memory_ram_used_v2, check_by_snmp_memory_swap_used_v2, check_by_snmp_memory_ram_used_v3, check_by_snmp_memory_swap_used_v3, check_by_snmp_memory_custom |
Description | Checks memory usage on Why? To monitor memory usage on hosts where you cannot install any agents. How? Collects monitored data over SNMP. |
/ platforms using SNMP.
Supported platforms | / |
Categories | SNMP, memory |
Support level | Level 5 (medium and bug support) |
Tags | unix, linux, snmp, net-snmp, memory, swap, buffer, cached |
check_by_snmp_procs
Commands | check_by_snmp_procs_total_number_of_processes_v2, check_by_snmp_procs_total_number_of_zombie_processes_v2, check_by_snmp_procs_process_by_name_v2, check_by_snmp_procs_cron_v2, check_by_snmp_procs_syslog_v2, check_by_snmp_procs_total_number_of_processes_v3 |
Description | Checks if and how many processes are running on the remote system. Why? To monitor processes on hosts where you cannot install any agents. How? Collects monitored data over SNMP. |
Supported platforms | / |
Categories | SNMP |
Support level | Level 5 (medium and bug support) |
Tags | unix, linux, snmp, net-snmp, process, processes |
check_by_ssh
Commands | check_by_ssh |
Description |
Executes commands on remote hosts. |
Supported platforms | Not platform dependent |
Categories | Misc |
Support level | Level 4 (high and fully supported) |
Tags | linux, unix, ssh, os |
check_citrix
Commands | check_citrix |
Description |
Checks if the Citrix master browser returns a published application list that contains names specified in the check command. |
Supported platforms | Not platform dependent |
Categories | Misc |
Support level | Level 5 (medium and bug support) |
Tags | citrix, published application, ica |
check_clamd
Commands | check_clamd |
Description |
Tests clamd connections with the specified host (or |
Supported platforms | Any host running clamd |
Categories | Misc |
Support level | Level 5 (medium and bug support) |
Tags | antivirus, clamd |
check_cloudwatch_status
Commands | check_cloudwatch_ec2_cpu_utilization, check_cloudwatch_ec2_network_in, check_cloudwatch_ec2_network_out, check_cloudwatch_ec2_disk_write_ops, check_cloudwatch_ec2_disk_write_bytes, check_cloudwatch_ec2_disk_read_ops, check_cloudwatch_ec2_disk_read_bytes, check_cloudwatch_elb_latency, check_cloudwatch_elb_request_count, check_cloudwatch_elb_healthy_host_count, check_cloudwatch_elb_unhealthy_host_count, check_cloudwatch_rds_cpu_utilization, check_cloudwatch_rds_free_storage_space, check_cloudwatch_rds_database_connections, check_cloudwatch_rds_read_iops, check_cloudwatch_rds_write_iops, check_cloudwatch_rds_read_latency, check_cloudwatch_rds_write_latency, check_cloudwatch_rds_read_throughput, check_cloudwatch_rds_write_throughput |
Description |
Monitors metrics from any instances in Amazon Web Services EC2, ELB, or RDS. |
Supported platforms |
Amazon Web Services |
Categories | Misc |
Support Level | Level 5 (medium and bug support) |
Tags | amazon, web services, aws, ec2, elb, rds, cpu, network, disk, load balancing |
check_cluster
Commands | check_cluster |
Description |
Used to check a cluster of services or hosts. |
Supported platforms | Not platform dependent |
Categories | Misc |
Support level | Level 5 (medium and bug support) |
Tags | clustered services, OP5 Monitor |
check_cmc
Commands | check_cmc |
Description |
Checks the temperature sensors of the Rittal CMC-TC monitoring system. |
Supported platforms | Rittal CMC-TC |
Categories | Environmental |
Support level | Level 6 (low and best effort) |
Tags | rittal, cmc-tc, environment, snmp |
check_compaq_insight
Commands | check_hp_insight |
Description |
Checks status of HP Insight hardware |
Supported platforms | HP Insight hardware (Proliant Series) |
Categories | Hardware |
Support level | Level 5 (medium and bug support) |
Tags | compaq, hp, insight, hardware, powersupply, fan, raid, snmp |
check_cpu_iowait_aix
Commands | check_cpu_iowait_aix |
Description |
Checks CPU IO wait on |
Supported platforms | |
Categories | CPU |
Support level | Level 6 (low and best effort) |
Tags | ibm, aix, cpu, iowait, iostat |
check_dell_openmanager
Commands | check_dell-openmanage, check_dell-openmanage_storage, check_dell-openmanage_blade, check_dell-openmanage_global, check_dell-openmanage_custom |
Description |
Checks the status of objects monitored by OpenManager on Dell servers using SNMP. |
Supported platforms | Dell servers with Dell OpenManager installed. |
Categories | Hardware |
Support level | Level 6 (low and best effort) |
Tags | dell, open manager, hardware, storage, powersupply, temperature, snmp |
check_dhcp
Commands | check_dhcp |
Description |
Tests functionality of a DHCP server. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support level | Level 4 (high and fully supported) |
Tags | dhcp, network, ip address |
check_dig
Commands | check_dig |
Description |
Checks DNS servers on a specific host using dig. |
Supported platforms | Not platform dependent |
Categories | DNS |
Support level | Level 4 (high and fully supported) |
Tags | dns, domain name, hostname, resolve |
check_disk
Commands | check_disk |
Description |
Checks disk usage on a mounted partition. |
Supported platforms | |
Categories | File system |
Support level | Level 4 (high and fully supported) |
Tags | linux, unix, file system, disk |
check_disk_smb
Commands | check_disk_smb |
Description |
Checks disk usage on SMB partitions. |
Supported platforms | Not platform dependent |
Categories | File system |
Support level | Level 4 (high and fully supported) |
Tags | microsoft windows, linux, samba, smb, disk |
check_dns
Commands | check_dns |
Description |
Checks DNS servers. |
Supported platforms | Not platform dependent |
Categories | DNS |
Support level | Level 4 (high and fully supported) |
Tags | dns, domain names, resolve |
check_docker
Commands | check_docker_cpu, check_docker_memory, check_docker_status, check_docker_health, check_docker_uptime, check_docker_image_age |
Description |
Checks Docker container status. |
Supported platforms |
Not platform dependent |
Categories | Containerisation |
Support Level | Level 6 (low and best effort) |
Tags | docker |
check_domain
Commands | check_domain_expiration |
Description |
Checks the expiration date of an domain name. |
Supported platforms | |
Categories | DNS |
Support level | Level 5 (medium and bug support) |
Tags | dns, domain names, whois |
check_dummy
Commands | check_dummy |
Description |
Returns whatever status and output you specify. Why? This can be used if you want to add hosts to your configuration that you cannot monitor but really want to include in the network map anyway. How? N/A |
Supported platforms | Not platform dependent |
Categories | Misc |
Support level | Level 4 (high and fully supported) |
Tags | dummy |
check_dummyv2
Commands | check_dummy |
Description |
Returns whatever status and output you specify. Why? This can be used if you want to add hosts to your configuration that you cannot monitor but really want to include in the network map anyway. How? N/A |
Supported platforms | Not platform dependent |
Categories | Misc |
Support level | Level 4 (high and fully supported) |
Tags | dummy |
check_ec2_status
Commands | check_ec2_status |
Description |
Checks the status of an instance on Amazon Web Services EC2. |
Supported platforms | Amazon Web Services |
Categories | Misc |
Support level | Level 8 (deprecated) |
Tags | amazon, aws, web service, ec2, host |
check_elasticquery
Commands | check_elasticquery |
Description | Checks Elasticsearch query total documents. It is designed to work with Energy Logserver and OP5 Log Analytics, open source Elasticsearch and X-Pack. Why? To check thresholds on saved searches from Elasticsearch. How? Queries the Elasticsearch REST API for information. |
Supported platforms | Not platform dependent |
Categories | Logs |
Support level | Level 4 (high and fully supported) |
Tags | logs, loganalytics |
check_em1
Commands | check_em1_humidity, check_em1_temperature, check_em1_wetness |
Description |
Check temperature, wetness, and humidity of a probe connected to a Sensatronics EM1. |
Supported platforms | Sensatronics EM1 |
Categories | Environmental |
Support level | Level 5 (medium and bug support) |
Tags | sensatronic, environment, humidity, wetness, temperature |
check_email_delivery
Commands | check_email_delivery, check_email_delivery_ssl, check_email_delivery_tls, check_email_delivery_smtp, check_email_delivery_imap, check_email_delivery_smtp_ssl, check_email_delivery_imap_ssl, check_email_delivery_smtp_tls, check_email_delivery_imap_tls, check_email_delivery_smtp_smtpauth, check_email_delivery_imap_smtpauth, check_email_delivery_smtp_ssl_smtpauth, check_email_delivery_imap_ssl_smtpauth, check_email_delivery_smtp_tls_smtpauth, check_email_delivery_imap_tls_smtpauth |
Description |
Sends email and verifies delivery. Why? The plugin checks full email send/delivery loop How? Sends email using SMTP and verifies delivery over IMAP. |
Supported platforms | Not platform dependent |
Categories | |
Support level | Level 4 (high and fully supported) |
Tags | email, imap, smtp, tls, ssl |
check_email_loop
Commands | check_email_loop |
Description |
Real end-to-end check of an email system.
Why? To verify end-to-end functionality of a complex email system. How? By sending email using SMTP and receiving emails from a mailbox over POP3 or IMAP. |
Supported platforms | Not platform dependent |
Categories | |
Support level | Level 5 (medium and bug support) |
Tags |
check_esx
Commands | check_esx |
Description |
Check status of VMware ESX server.
Why? The plugin checks the status (CPU, memory) of virtual machines running inside a VMware ESX server. How? The plugin queries the status of the ESX server using SNMP. |
Supported platforms | VMware ESX server |
Categories | Operating systems |
Support level | Level 6 (low and best effort) |
Tags | vmware, esx, snmp |
check_exchange
Commands | check_exchange_services, check_exchange_performance_counters |
Description |
Combines several tests to create a reliable set of services that together provide the complete picture of a Microsoft exchange server's status.
|
Supported platforms | |
Categories | |
Support level | Level 4 (high and fully supported) |
Tags | email, microsoft exchange |
check_file
Commands | check_sms_failed (sms) |
Description |
Checks the age and size of a file. It can also be used to monitor the number of files of a specific type in a folder. Why? To keep track of files and folders. For example, by making sure a specific file does not get too large. How? By checking the age and size of files and the number of files in folders. |
Supported platforms | / |
Categories | File system |
Support level | Level 4 (high and fully supported) |
Tags | unix, linux, file, file system |
check_file_age
Commands | check_file_age |
Description |
Checks the age of a file. Why? This can be useful if you have a file that is updated at specific intervals. Using this plugin, you can be notified if the update does not happen. How? By looking at the attribute data on the file. |
Supported platforms | |
Categories | File system |
Support level | Level 4 (high and fully supported) |
Tags | file, file system, unix, linux |
check_flexlm
Commands | check_flexlm |
Description |
Checks available FLEXlm licence managers.
Why? In order not to run out of available licences. How? By using the lmstat program. |
Supported platforms | |
Categories | Misc |
Support level | Level 4 (high and fully supported) |
Tags | unix, lmstat, flexlm license |
check_fping
Commands | check_fping |
Description |
Checks a list of hosts over ICMP to check if they are alive or not.
Why? Can be used to monitor a set of hosts to monitor if they are alive or not. How? This plugin uses the fping command to ping the specified host(s) for a fast check. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support level | Level 4 (high and fully supported) |
Tags | Icmp, ping, host |
check_ftp
Commands | check_ftp |
Description |
Checks the status of an FTP server.
Why? To ensure the FTP server is working. How? By connecting to the FTP server and checking for a correct response. You can also set thresholds on response time. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support level | Level 4 (high and fully supported) |
Tags | ftp, tcp |
check_host
Commands | check-host-alive |
Description |
Checks status of a host.
Why? To verify that the host is alive. How? By using ICMP. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support level | Level 4 (high and fully supported) |
Tags | host, icmp, network |
check_hpasm
Commands | check_hp_proliant_hardware_remote, check_hp_bladesystem_hardware_remote |
Description |
Checks the status of HP Proliant servers and HP Blade systems.
Why? To check the status of processors, power supplies, memory modules, fans, temperature, and RAIDs on your HP machines. How? The plugin can either query a remote machine over SNMP or be executed locally. It needs to have HP ASM installed on the server to be able to get the information needed. If you run it locally on HP servers, you need to have the command hpasmcli installed. |
Supported platforms | HP Proliant, HP Blade systems |
Categories | Hardware |
Support level | Level 5 (medium and bug support) |
Tags | hp, insight, hardware, powersupply, fan, raid, snmp, blade system, temperature |
check_hpjd
Commands | check_hpjd, check_hpjd_public |
Description |
Checks the status of an HP printer with a Jetdirect card.
Why? To keep track of problems with your HP printers. How? By using SNMP. |
Supported platforms | HP printers with a Deskjet card |
Categories | Printers |
Support level | Level 5 (medium and bug support) |
Tags | hp, printer, jetdirect, snmp |
check_http
Commands |
check_http, check_https, check_https_auth, check_https_auth_url, check_https_certificate, check_https_port, check_https_port_url, check_https_timeout, check_https_timeout_url, check_https_url, check_https_url_regex, check_https_url_string, check_https_vhost, check_https_vhost_certificate, check_https_vhost_url_string, check_http_auth, check_http_auth_url, check_http_port, check_http_port_url, check_http_timeout, check_http_timeout_url, check_http_url, check_http_url_regex, check_http_url_string, check_http_vhost, check_http_vhost_url_string |
Description |
Checks status of a web server
|
Supported platforms | Not platform dependent |
Categories | Networking, Web |
Support level | Level 4 (high and fully supported) |
Tags | http, web, https, ssl, url |
check_http_xpath
Commands | check_http_xpath, check_http_xpath_ssl, check_http_xpath_custom |
Description |
Checks and XML web page for content using the XML XPath syntax.
Why? To check for the presence or absence of specific content in an XML document which is retrieved using HTTP. How? The text to search for is specified in XML XPath format at the command line. Multiple XPath checks can be performed in one operation. Checks can be any of == != > < <= >= =~ !~. If no operator is specified, the XPath must simply exist. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support level | Level 5 (medium and bug support) |
Tags | http, xpath, xml |
check_icmp
Commands | check-host-alive-icmp, check_ping, check_ping_critical, check_ping_normal |
Description |
Checks RTA and packet loss using ICMP.
Why? To see status and reachability on your network. How? Checks connectivity on the network using ICMP. It lets you specify thresholds for RTA and loss, and also how many packets to send, packetsize, TTL, interval between packets, and timeout. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support level | Level 4 (high and fully supported) |
Tags | host, icmp, ping, packet loss, rta |
check_ide_smart
Commands | check_ide_smart |
Description |
Checks a local hard drive with a Why? To get control over the local hard drives on your server. How? By checking the local hard drive with ioctl. |
specific smart interface.
Supported platforms | host with the smart interface installed |
Categories | Hardware |
Support level | Level 5 (medium and bug support) |
Tags | hardware, storage, ide, smart, linux |
check_iferrors
Commands | check_iferrors |
Description |
Checks for errors on a network interface.
Why? To be notified of and locate network problems. How? By using SNMP. You can specify thresholds on the amount of errors. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support level | Level 5 (medium and bug support) |
Tags | network, interface errors, snmp |
check_ifoperstatus
Commands | check_ifoperstatus |
Description |
Checks the operational status of a network interface.
Why? To monitor the status of a network port. How? By using SNMP. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support level | Level 4 (high and fully supported) |
Tags | switch, router, network, interface status, snmp |
check_ifstatus
Commands | check_ifstatus |
Description |
Checks the operational status of all network interfaces on a host.
Why? To monitor the status of network ports. How? By using SNMP. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support level | Level 5 (medium and bug support) |
Tags | network, snmp, interface status, switch, router |
check_imap
Commands | check_imap |
Description |
Checks connectivity to an IMAP server.
Why? To monitor the status of an IMAP mail server. How? By connecting to the IMAP server. You can send IMAP commands to the server and specify the expected response. You can also set thresholds on response time. |
Supported platforms | Not platform dependent |
Categories | |
Support level | Level 4 (high and fully supported) |
Tags | email, imap |
check_internet
Commands | check_internet |
Description |
Takes a number of internet sites and checks if any one of them are alive.
Why? The plugin can be used to monitor your internet connection and alert you if it is down. How? It is a wrapper around check_http. It takes every internet site sent as an argument to check_internet and executes a simple check_http check with the timeout set to 5 seconds. |
Supported platforms | Not platform dependent |
Categories | Networking, web |
Support level | Level 4 (high and fully supported) |
Tags | internet, network, web |
check_ipmi
Commands | Internet, network, web |
Description | Nagios plugin for locally checking hardware status (fans, voltage) via IPMI.
Why? To monitor the local hardware on your server. How? Uses ipmitool to get results from the kernel. |
Supported platforms | server with ipmitool installed |
Categories | Hardware |
Support level | Level 4 (high and fully supported) |
Tags | ipmi, ipmitool, unix, linux, local hardware |
check_ipmi_sensors
Commands | check_ipmi_sensor_fan, check_ipmi_sensor_platform_sequrity, check_ipmi_sensor_power_supply, check_ipmi_sensor_power_unit, check_ipmi_sensor_memory, check_ipmi_sensor_drive_slot, check_ipmi_sensor_system_firmware_progress, check_ipmi_sensor_system_event, check_ipmi_sensor_critical_interrupt, check_ipmi_sensor_module_board, check_ipmi_sensor_slot_connector, check_ipmi_sensor_temperature, check_ipmi_sensor_current, check_ipmi_sensor_voltage, check_ipmi_sensor_processor, check_ipmi_sensor_watchdog2, check_ipmi_sensor_physical_security |
Description |
plugin for checking hardware status (for example, fans and voltage). Locally or remotely using freeipmi.
Why? To monitor the hardware on your server. |
Supported platforms | Devices supporting IMPI using serial over LAN |
Categories | Hardware |
Support level | Level 5 (medium and bug support) |
Tags | ipmi, hardware, linux, freeipmi, linux |
check_ircd
Commands | check_ircd |
Description |
Checking to see if there is an IRCd running and see how many users it has. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support level | Level 4 (high and fully supported) |
Tags | irc server, chat |
check_jabber
Commands | check_jabber |
Description |
Tests jabber connections to a specified host.
Why? To monitor the status of a message server running Jabber. How? By connecting to the Jabber server. You can send a message and check for a proper response. You can also specify to use SSL and set a threshold on response time. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support level | Level 4 (high and fully supported) |
Tags | jabber, im, chat Jabber, im, chat |
check_jmx
Commands | check_jmx_current_threadcount, check_jmx_garbage_collection_timing, check_jmx_heapmem_used, check_jmx_long_running_threads, check_jmx_nonheap_mem_used, check_jmx_availible_connections_in_pool |
Command references | check_jmx |
Description |
The JMX plugin is a Nagios plugin for monitoring devices, applications, and service-driven networks using Java Management Extensions (JMX).
JMX is a Java technology that supplies tools for managing and monitoring applications, system objects, devices, such as printers, and service oriented networks. Those resources are represented by objects called mbeans (for managed bean). JMX exposes a set of mbeans which represent a resource running in the Java Virtual Machine. The JMX implementation of a Java application server typically exposes resource usage statistics (such as memory or threads used) and lots of other statistics and metrics. Apart from generic information, the application server vendor also provides mbeans specific to the application server in question. The check_jmx plugin enables you to monitor the values of any mbean attribute made available through JMX. |
Categories | Java |
Support level | Level 5 (medium and bug support) |
Tags | jmx, java, jboss, web application |
check_json
Commands | check_json, check_json_perfvars, check_json_custom |
Description |
Checks an HTTP server for JSON attributes. |
Supported platforms |
Not platform dependent |
Categories | Networking |
Support Level | Level 5 (medium and bug support) |
Tags | http, json |
check_k8s
Commands | check_k8s_nodes, check_k8s_pods, check_k8s_deployments |
Description |
Support for monitoring Kubernetes clusters. |
Supported platforms |
Not platform dependent |
Categories | Containerisation |
Support Level | Level 6 (low and best effort) |
Tags | kubernetes |
check_ldap
Commands | check_ldap |
Description |
Tests connections to an LDAP server.
Why? To ensure the LDAP server is working. This can be used to check, for example, Active Directory Servers. How? By connecting to the LDAP server, you can specify protocol version, password, and different search criteria. You can also set thresholds on response time. |
Supported platforms | Not platform dependent |
Categories | Misc |
Support level | Level 4 (high and fully supported) |
Tags | ldap |
check_ldaps
Commands | check_ldaps |
Description |
Tests connections to an LDAPS server.
Why? To ensure that the LDAPS server is working. This can be used to check, for example, Active Directory servers. How? By connecting to the LDAPS server. You can specify protocol version, password, and different search criteria. You can also set thresholds on response time |
Supported platforms | Not platform dependent |
Categories | Misc |
Support level | Level 4 (high and fully supported) |
Tags | ldap, secure ldap |
check_libvirt
Commands | check_libvirt_kvm_guest_cpu, check_libvirt_kvm_guest_mem, check_libvirt_kvm_guest_disk_io, check_libvirt_kvm_guest_net_io, check_libvirt_kvm_guest_running, check_libvirt_kvm_host_running, check_libvirt_kvm_host_storage_pool, check_libvirt_kvm_host_volume_all, check_libvirt_kvm_host_volume, check_libvirt_xen_guest_cpu, check_libvirt_xen_guest_disk_io, check_libvirt_xen_guest_mem, check_libvirt_xen_guest_net_io, check_libvirt_xen_guest_running, check_libvirt_xen_host_running, check_libvirt_xen_host_storage_pool, check_libvirt_xen_host_volume, check_libvirt_xen_host_volume_all |
Description |
Check status of KVM or XEN servers.
Why? The plugin checks the status (for example, CPU, memory, disk IO) of virtual machines running inside KVM or XEN servers and the hosts. How? The plugin queries the status of KVM or XEN servers using the libvirt virtualization API. |
Supported platforms | KVM server, XEN server |
Categories | Operating systems |
Support level | Level 4 (high and fully supported) |
Tags | kvm, xen, libvirt, virtualization, os |
check_linux_stats
Commands | check_nrpe_linux_cpu_usage_idle, check_nrpe_linux_cpu_usage_iowait, check_nrpe_linux_cpu_usage_nice, check_nrpe_linux_cpu_usage_steal, check_nrpe_linux_cpu_usage_system, check_nrpe_linux_cpu_usage_total, check_nrpe_linux_cpu_usage_user, check_nrpe_linux_disk_io_requests, check_nrpe_linux_disk_usage_root, check_nrpe_linux_disk_usage_all, check_nrpe_linux_linux_total_open_sockets, check_nrpe_linux_load, check_nrpe_linux_mem_and_swap, check_nrpe_linux_network, check_nrpe_linux_paging_in_out, check_nrpe_linux_total_open_files_inodes, check_nrpe_linux_total_processes, check_nrpe_linux_uptime |
Description |
Monitors CPU, disk, IO, processes, paging, and a lot more, on a Why? To monitor your server. How? The plugin needs to be used locally on the host you want to monitor, and the plugin needs to be executed using NRPE. Before you can use the plugin, you need to have install the following Perl module on the system where the plugin will be executed: Sys::Statistics::Linux |
host.
Supported platforms | |
Categories | Operating systems |
Support level | Level 4 (high and fully supported) |
Tags | linux, cpu, memory, io, files, processes, paging, swap, disk |
check_load
Commands | check_load |
Description |
Checks system load on a Why? To check for problems with the capacity of a server, to determine if and when you need to upgrade. How? By checking the number of jobs in the processor queue. A load of 1 means that the processor always has one job in the queue on a single processor system. The plugin lets you specify thresholds on load values. |
server.
Supported platforms | |
Categories | CPU |
Support level | Level 4 (high and fully supported) |
Tags | unix, linux, cpu, load |
check_load_by_w
Commands | check_load_by_w |
Description |
Checks system load on a Why? To ensure the system load does not become too high. How? Checking the load on a or a server, by using the w command. |
server.
Supported platforms | / |
Categories | CPU |
Support level | Level 6 (low and best effort) |
Tags | unix, linux, cpu, load |
check_log
Commands | check_log |
Description |
Checks log files on the How? Scans a specific log file for a specific pattern, as specified by options. Successive calls to the plugin script only report new pattern matches in the log file, since a copy of the log file from the previous run is saved. |
system.
Supported platforms | |
Categories | Logs |
Support level | Level 4 (high and fully supported) |
Tags | linux, unix, logs |
check_log2
Commands | check_log, check_log_eventlog, check_log_snmptraps, check_log_syslog |
Description |
Smart logfile checker for Why? To automatically keep track of error messages that are only visible in a log file. How? This plugin starts searching the log file where it stopped on the last check, so it does not need to go through the whole file. You can specify search patterns both as normal text and as a regular expression. |
systems.
Supported platforms | |
Categories | Logs |
Support level | Level 5 (medium and bug support) |
Tags | unix, linux, logs |
check_logfiles
Commands | check_logfiles |
Description |
check_logfiles scans log files for specific patterns. Why? To check for and be notified of errors or other specified messages in your log files. |
Supported platforms | |
Categories | Logs |
Support level | Level 6 (low and best effort) |
Tags | logs |
check_logserver
Commands | check_logserver |
Description |
Monitors the number of log files that were placed in the op5-logserver error directory. Why? To check how many logs are placed in the error directory. How? By opening the error directory and counting the number of files. |
Supported platforms | OP5 logserver |
Categories | Logs |
Support level | Level 4 (high and fully supported) |
Tags | op5 logserver, error logs |
check_ls_log
Commands | check_op5_logserver_filter, check_op5_logserver_filter_static_interval, check_ls_log |
Description |
Checks the status of predefined filters in op5-logserver versions greater than 2.1. |
Supported platforms | Op5 logserver |
Categories | Logs |
Support level | Level 4 (high and fully supported) |
Tags | op5 logserver, logs |
check_ls_log_2_1
Commands | check_ls_log_2_1 |
Description |
Checks the status of predefined filters in op5-logserver version 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. |
Supported platforms | OP5 logserver |
Categories | Logs |
Support level | Level 4 (high and fully supported) |
Tags | op5 logserver, logs |
check_mailq
Commands | check_mailq |
Description |
Checks the number of mails in a mail queue in Why? To identify problems with the mail system. How? Searches through mailq and lets you specify minimum and maximum allowed mails in the queue. Supports Sendmail, qmail, PostFix and Exim. |
mail systems.
Supported platforms | |
Categories | |
Support Level | Level 4 (high and fully supported) |
Tags | email, local mail queue, sendmail, qmail, postfix, exim, unix, linux |
check_maxdb
Commands | check_maxdb |
Description |
Checks the status of your MaxDB servers. Why? To ensure your MaxDB servers are up and running. How? Connects to the MaxDB database with the command dbmcli and parses the result. It can check problems with backups, log fillrates, and custom strings in the info state result set. |
Categories | Databases |
Support Level | Level 6 (low and best effort) |
Tags | database, maxdb |
check_megaraid
Commands | check_megaraid |
Description | Locally checks the status of a MegaRAID controller. Why? To monitor the local MegaRAID controller on your server is working as expected. How? Uses the /proc/megaraid/ directory to find out the disk status. |
Supported platforms | / using MegaRAID |
Categories | Hardware |
Support Level | Level 6 (low and best effort) |
Tags | megaraid, raid controller, hardware |
check_movex
Commands | check_movex |
Description | Checks different Movex M3 related system information. How? By connecting to the M3 web server and retrieving relevant URLs. |
Supported platforms | Movex M3 systems |
Categories | ERP systems |
Support Level | Level 6 (low and best effort) |
Tags | movex, m3 |
check_mrtg
Commands | check_mrtg |
Description | Monitors data in an MRTG log file. Why? If you have MRTG installed and want to monitor the contents of a graph. How? By looking for a value in the specified log file. You can also set thresholds. This plugin only searches for one single value in the log file. |
Supported platforms | |
Categories | Misc |
Support Level | Level 6 (low and best effort) |
Tags | mrtg |
check_mrtgtraf
Commands | check_mrtgtraf |
Description | Checks for traffic usage in an MRTG traffic graph log file. Why? If you have MRTG installed and want to monitor the traffic usage, not by polling the router/switch but using MRTG instead. How? By looking in the log file and specifying thresholds for incoming and outgoing traffic. |
Supported platforms | |
Categories | Misc |
Support Level | Level 6 (low and best effort) |
Tags | mrtg, network, traffic |
check_mssql
Commands | check_mssql_db_online, check_mssql_query_response, check_mssql_response_length, check_mssql_blocked_processes, check_mssql_blocked_processes_ad_user, check_sybase_db_online, check_sybase_query_response, check_sybase_response_length |
Description | 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. |
Supported platforms | |
Categories | Databases |
Support Level | Level 4 (high and fully supported) |
Tags | microsoft windows, sql server, database |
check_mssql_health
Commands | check_mssql_health_cpu-busy, check_mssql_health_io-busy, check_mssql_health_full-scans, check_mssql_health_connected-users, check_mssql_health_transactions_all, check_mssql_health_transactions, check_mssql_health_batch-requests, check_mssql_health_latches-waits, check_mssql_health_latches-wait-time, check_mssql_health_locks-waits, check_mssql_health_locks-timeouts, check_mssql_health_locks-deadlocks, check_mssql_health_sql-recompilations, check_mssql_health_sql-initcompilations, check_mssql_health_total-server-memory, check_mssql_health_mem-pool-data-buffer-hit-ratio, check_mssql_health_lazy-writes, check_mssql_health_page-life-expectancy, check_mssql_health_free-list-stalls, check_mssql_health_checkpoint-pages, check_mssql_health_database-online_all, check_mssql_health_database-online, check_mssql_health_database-free_all, check_mssql_health_database-free, check_mssql_health_database-backup-age_all, check_mssql_health_database-backup-age, check_mssql_health_database-logbackup-age_all, check_mssql_health_database-logbackup-age, check_mssql_health_database-file-auto-growths_all, check_mssql_health_database-file-auto-growths, check_mssql_health_database-logfile-auto-growths_all, check_mssql_health_database-logfile-auto-growths, check_mssql_health_database-datafile-auto-growths_all, check_mssql_health_database-datafile-auto-growths, check_mssql_health_database-file-auto-shrinks_all, check_mssql_health_database-file-auto-shrinks, check_mssql_health_database-logfile-auto-shrinks_all, check_mssql_health_database-logfile-auto-shrinks, check_mssql_health_database-datafile-auto-shrinks_all, check_mssql_health_database-datafile-auto-shrinks, check_mssql_health_database-file-dbcc-shrinks_all, check_mssql_health_database-file-dbcc-shrinks, check_mssql_health_failed-jobs, check_mssql_health_sql, check_mssql_health_sql-runtime, check_mssql_health_list-databases, check_mssql_health_list-datafiles, check_mssql_health_list-locks |
Description |
Checks Microsoft SQL servers. |
Supported platforms | |
Categories | Databases |
Support Level | Level 4 (high and fully supported) |
Tags | microsoft windows, sql server, database |
check_multiurl
Commands | check_multiurl |
Description | Retrieves a list of URLs and checks them in parallel. How? Uses wget to retrieve the list of URLs to be checked. check_http is then used to check the URLs. |
Supported platforms | No platform dependency |
Categories | Networking, web |
Support Level | Level 4 (high and fully supported) |
Tags | web, network, http |
check_mysql_health
Commands | check_mysql_health_connection-time, check_mysql_health_uptime, check_mysql_health_threads-connected, check_mysql_health_threadcache-hitrate, check_mysql_health_threads-created, check_mysql_health_threads-running, check_mysql_health_threads-cached, check_mysql_health_connects-aborted, check_mysql_health_clients-aborted, check_mysql_health_slave-lag, check_mysql_health_slave-io-running, check_mysql_health_slave-sql-running, check_mysql_health_qcache-hitrate, check_mysql_health_qcache-lowmem-prunes, check_mysql_health_myisam_keycache-hitrate, check_mysql_health_innodb_bufferpool-hitrate, check_mysql_health_innodb_bufferpool-wait-free, check_mysql_health_innodb_log-waits, check_mysql_health_tablecache-hitrate, check_mysql_health_table-lock-contention, check_mysql_health_index-usage, check_mysql_health_tmp-disk-tables, check_mysql_health_table-fragmentation_all, check_mysql_health_table-fragmentation, check_mysql_health_open-files, check_mysql_health_slow-queries, check_mysql_health_long-running-procs, check_mysql_health_cluster-ndbd-running, check_mysql_health_sql_query, check_mysql_health_sql_query_custom_units |
Description | Tests various parameters of a MySQL database. You can also use custom SQL queries that return a single number. Why? To identify problems with MySQL database servers or specific databases. Can also be used to monitor the data you have in your databases. How? Connects to a MySQL server and checks the status mainly, using the MySQL show status command. |
Supported platforms | Not platform dependent |
Categories | Databases |
Support Level | Level 4 (high and fully supported) |
Tags | mysql, database |
check_mysql_query
Commands | check_mysql_query |
Description | This plugin is deprecated in OP5 Monitor >
This program checks a query result against threshold levels. Why? So you can send custom queries to a MySQL database. How? You send an SQL query and make sure it returns a numeric value. |
Supported platforms | Anything that can run a MySQL server |
Categories | Databases |
Support Level | Level 8 (deprecated) |
Tags | mysql, database, sql query |
check_nagios
Commands | check_nagios |
Description |
Checks the status of the Nagios process on the local machine. |
Supported platforms | OP5 Monitor Nagios | server running
Categories | Misc |
Support Level | Level 4 (high and fully supported) |
Tags | unix, linux, nagios, op5 monitor core |
check_new_ents
Commands | check_new_ents |
Description | The plugin looks for the latest file in a folder and informs you when the file was last changed. Why? It can be useful for informative monitoring such as transaction files and backup files. How? By looking in a specified folder for the latest file and picking up the latest change time stamp from the file attributes. |
Supported platforms | / |
Categories | File system |
Support Level | Level 5 (medium and bug support) |
Tags | file system, unix, linux |
check_nntp
Commands | check_nntp |
Description | Tests NNTP connections. Why? To catch problems with an NNTP server How? Connects to an NNTP host to test the connection. You can also specify response time thresholds. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support Level | Level 4 (high and fully supported) |
Tags | nntp, news server |
check_nntps
Commands | check_nntps |
Description | Tests SNNTP connections. Why? To catch problems with an SNNTP server How? Connects to an SNNTP host to test the connection. You can also specify response time thresholds. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support Level | Level 4 (high and fully supported) |
Tags | snntp, news server |
check_nrpe
Commands | check_nrpe, check_nrpe_disk_root, check_nrpe_disk_var, check_nrpe_load, check_nrpe_proc_crond, check_nrpe_proc_named, check_nrpe_proc_syslogd, check_nrpe_proc_total, check_nrpe_proc_zombie, check_nrpe_swap, check_nrpe_users, check_mssql_buffer_cache_hit_ratio |
Description | Checks remote NRPE. Why? To be able to check the status of remote hosts. How? Runs plugins on remote servers running NRPE. You can use check_nrpe to run all plugins that normally only check statuses on a local server. You can also run checks to test the network from a remote server instead of from the OP5 Monitor server. What you can check is configured in the nrpe.cfg configuration file on the remote server and the set of plugins on the remote server. |
servers running
Supported platforms | |
Categories | Misc |
Support Level | Level 4 (high and fully supported) |
Tags | nrpe, unix, linux |
check_nt
Commands | check-host-alive-nsclient, check_nt_clientversion, check_nt_cpuload, check_nt_disk, check_nt_memuse, check_nt_pagingfile, check_nt_process, check_nt_service, check_nt_uptime, check_mssql_db_file_size, check_mssql_log_file_size, check_nt_memory_page_per_sec, check_nt_physical_disk_time, check_mssql_cache_hit_ratio, check_mssql_num_deadlocks, check_mssql_num_user_connections, check_perf_phys_disk_time, check_perf_avg_disk_queue_length, check_perf_io_read, check_perf_io_write, check_perf_memory_pages_per_sec, check_perf_proc_elapsed_time, check_perf_proc_id_process, check_perf_proc_pagefile_bytes, check_perf_proc_page_faults, check_perf_proc_pool_nonpaged_bytes, check_perf_proc_pool_paged_bytes, check_perf_proc_priority_base, check_perf_proc_private_bytes, check_perf_proc_thread_count, check_perf_proc_virtual_bytes, check_perf_terminal_active_sessions, check_perf_terminal_inactive_sessions, check_perf_terminal_total_sessions |
Description | Checks remote NSClient++. Why? To monitor the status of your servers. How? Connects to the NSClient++ service and retrieves the following information: CPU usage, memory usage, swap usage, disk usage, process status, service status. It also allows you to run queries against performance counters. |
servers running
Supported platforms | |
Categories | Operating systems |
Support Level | Level 6 (low and best effort) |
Tags | microsoft windows, nsclient |
check_ntp_peer
Commands | check_ntp_server, check_ntp_stratum |
Description | Checks the health of an NTP server. Check the health of an ntp server. Why? To make sure the NTP server is in sync with its peers. How? Checks the health of an NTP server. Allows you to set thresholds on accepted offset, jitter, and stratum. |
Supported platforms | Not platform dependent |
Support Level | Level 4 (high and fully supported) |
Tags | ntp, time |
check_ntp_time
Commands | check_ntp_time |
Description | Checks the clock offset between the local host and a remote NTP server. Why? To keep track of server clocks. How? Connects to an NTP server and compares the NTP clock to the local clock. Lets you set thresholds on accepted offset. |
Supported platforms | Not platform dependent |
Support Level | Level 4 (high and fully supported) |
Tags | ntp, time |
check_nwstat
Commands | check_nwstat, check_nwstat_conns, check_nwstat_load1, check_nwstat_load15, check_nwstat_load5, check_nwstat_uprb |
Description | Checks remote Novell NetWare servers running mrtgext.nlm. Why? To check the status of your NetWare servers. How? Connects to the mrtgext nlm and gathers information about CPU usage, disk usage, and other things. |
Supported platforms | Novell NetWare |
Categories | Operating systems |
Support Level | Level 5 (medium and bug support) |
Tags | novel, netwrare, mrtget, os |
check_om_chassis
Commands | check_om_chassis |
Description | Checks chassis state of Dell servers using the omreport command from the Dell OpenManage distribution. Why? To ensure you will be notified if there is a chassis problem with your Dell server. How? Communication between OP5 Monitor and Dell OpenManage is performed by SNMP. |
Supported platforms | Dell servers |
Categories | Hardware |
Support Level | Level 5 (medium and bug support) |
Tags | dell, hardware, open manager, chassis |
check_om_storage
Commands | check_om_storage |
Description | Checks the state of Dell storage using the omreport command from the Dell OpenManage distribution. Why? To ensure you will be notified if there is a problem with the storage on your Dell server. How? Communication between OP5 Monitor and Dell OpenManage is performed by SNMP. |
Supported platforms | Dell servers |
Categories | Hardware |
Support Level | Level 5 (medium and bug support) |
Tags | dell, hardware, open manager, storage |
check_op5_filter
Commands | check_op5_listview_filter, check_op5_listview_filter_auth_file, check_op5_listview_filter_custom_status_label, check_op5_listview_filter_custom_status_label_auth_file, check_op5_listview_log_messages_filter, check_op5_listview_log_messages_filter_msg_last_servicecheck, check_op5_listview_log_messages_filter_auth_file, check_op5_listview_log_messages_filter_custom_host, check_op5_listview_log_messages_filter_custom_host_auth_file |
Description | Allows you to monitor OP5 Monitor list view filters. The plugin counts the number of hits you get from a filter you provide. It is mainly to be used for monitoring logserver filters in OP5 Monitor, but can be used for other types of list views as well. Why? To monitor the content of log data sent to the OP5 Monitor logserver extension. How? The plugin connects to the OP5 Monitor API and queries the filter provided as the plugin argument. |
Supported platforms | OP5 Monitor server |
Support Level | Level 4 (high and fully supported) |
Tags | op5, list view, filter, logserver |
check_op5_license
Commands | check_op5_license_monitor_percentage_left, check_op5_license_monitor_hosts_left, check_op5_license_monitor_days_left |
Description | Notifies you when your license expires. |
Support Level | Level 4 (high and fully supported) |
Tags | op5 |
check_op5backup2
Commands | check_op5backup_state |
Description | Checks the backup process state. Why? To notify you about latest backup process state. How? Checks the latest backup log. |
Supported platforms |
Any server running OP5 Monitor |
Categories | Backup |
Support Level | Level 4 (high and fully supported) |
Tags | op5, backup |
check_op5monitor
Commands | check_merlin_mysql, check_merlin_mysql_virt_mem_usage, check_merlin_process, check_merlin_process_cpu_usage, check_merlin_process_virt_mem_usage, check_merlin_prog_status, check_monitor_core_files, check_monitor_distribution, check_monitor_failed_sms, check_monitor_hardware_ipmi, check_monitor_host_check_exec_time, check_monitor_host_check_orphans, check_monitor_host_latency, check_monitor_op5backup, check_monitor_pnp_graph_procs, check_monitor_processes, check_monitor_processes_cpu_usage, check_monitor_rrdcached_proc, check_monitor_service_check_exec_time, check_monitor_service_check_orphans, check_monitor_service_latency, check_monitor_smsd_procs, check_monitor_smsd_zombie_procs, check_monitor_spooled_checks, check_monitor_spooled_perfdata, check_monitor_tmp_disk, check_monitor_yum_update |
Description | This is a collection of commands to be used to monitor your OP5 Monitor server. Why? The commands included to get an overall picture of your OP5 Monitor server. How? All commands use NRPE. If you are running a peered solution, you need to check the correct OP5 Monitor server no matter which peer is executing the check. |
Supported platforms | Any server running OP5 Monitor |
Categories | OP5 Monitor servers |
Support Level | Level 4 (high and fully supported) |
Tags | op5 monitor |
check_openmanage
Commands | check_openmanage |
Description | Checks the status of objects monitored by OpenManager on Dell servers using SNMP or
tool omreport. Why? To notify you of problems with the hardware on your Dell servers. How? Checks temperature, disks (RAID), power supply and more through SNMP. |
Supported platforms | Dell servers with Dell OpenManager installed |
Categories | Hardware |
Support Level | Level 4 (high and fully supported) |
Tags | dell, open manager, hardware |
check_oracle
Commands | check_oracle_dummy_login, check_oracle_login, check_oracle_cache_hit_ratio, check_oracle_cache_hit_ratio_all, check_oracle_query, check_oracle_query_regex |
Description | Checks the status of an Oracle database. Why? To monitor the status of your Oracle databases. |
Supported platforms | |
Categories | Databases |
Support Level | Level 4 (high and fully supported) |
Tags | database, oracle |
check_overcr
Commands | check_overcr |
Description | Gathers over-cr collector daemon data. Why? To remotely gather system information. How? Connects to the over-cr daemon running on a remote host. |
Supported platforms | |
Categories | Misc |
Support Level | Level 5 (medium and bug support) |
Tags | over-cr collector, unix, linux, network |
negate
Commands | negate |
Description | Negates the result of a plugin. Why? For example, if you want to check that it is not possible to connect to a specific TCP port, you can use check_tcp, which will return critical as long as the port is closed. negate converts that response to ok. How? The plugin needs to be used with other plugins, and negates the check result. |
Supported platforms | Not platform dependent |
Categories | Misc |
Support Level | Level 4 (high and fully supported) |
Tags | negate result |
check_pattern
Commands | check_pattern |
Description | Checks a log file on the local host for a given pattern. Why? To search for certain rows or patterns in your log files. How? By searching for a beginning pattern and an end pattern and by default only look at the last found matching entry. |
Supported platforms | / |
Categories | Logs |
Support Level | Level 4 (high and fully supported) |
Tags | log file, unix, linux, pattern, logs |
check_pf
Commands | check_pf |
Description | Checks hardware, for example fan and CPU, on your PacketFront CPS router. Why? To make sure the hardware on your PacketFront router works as expected. How? By SNMP. |
Supported platforms | PacketFront routers |
Categories | Hardware, networking |
Support Level | Level 5 (medium and bug support) |
Tags | router, packetfront, cps, hardware, network |
check_pgsql
Commands | check_pgsql |
Description | Checks the status of a Postgresql database. Why? So you can keep track of the status of your Postgresql databases. How? Connects to a Postgresql database and checks if it is accepting connections. You can specify database, user name, and password and also to set thresholds on response times. |
Supported platforms | Not platform dependent |
Categories | Databases |
Support Level | Level 4 (high and fully supported) |
Tags | postgresql, database |
check_ping
Commands | check_ping |
Description | Checks a number of given hosts to see if they are alive. Why? To test the connectivity to a number of hosts at the same time. How? Checks over ICMP and if any of the hosts are down the result is critical. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support Level | Level 4 (high and fully supported) |
Tags | icmp, ping, network |
check_pop
Commands | check_pop |
Description | Checks the status of a POP3 server. Why? To see the status of your POP3 servers. How? Connects to a POP3 server and checks the status. |
Supported platforms | Not platform dependent |
Categories | |
Support Level | Level 4 (high and fully supported) |
Tags | email, pop, tcp |
check_portstatus
Commands | check_portstatus, check_portstatus_dormant |
Description | Keeps track of the number of unused switch ports. Why? To help you get control of the ports used by your switches. How? By SNMP. |
Supported platforms | Switches |
Categories | Networking |
Support Level | Level 4 (high and fully supported) |
Tags | network, switch, router, switch ports, snmp |
check_procs
Commands | check_procs |
Description | Checks the status of processes. Why? To test important applications are running. How? Checks the number of running processes. Lets you configure thresholds for the number of processes allowed to run. You can also check for a specific process, processes of a specific user, and different process states. |
Supported platforms | |
Categories | Misc |
Support Level | Level 4 (high and fully supported) |
Tags | unix, linux, process, states |
check_radius
Commands | check_radius |
Description | Checks the status of a radius server. Why? To ensure that your radius server is working. How? Simulates a connection from a NAS to a radius server. Lets you specify user name, password, and NAS identifier. You can also specify the expected response and timeout. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support Level | Level 4 (high and fully supported) |
Tags | radius, network |
check_real
Commands | check_real |
Description | Tests the real service on a host. Why? To see the status of your real media server. How? Attempts to open an RTSP connection with the host. Successful connections return state_ok, connection refusals and timeouts return state_critical, other errors return state_unknown. Incorrect reponse messages from the host result in state_warning return values. |
Supported platforms | Real media server |
Categories | Misc |
Support Level | Level 4 (high and fully supported) |
Tags | real media server, rtsp |
check_route
Commands | check_route |
Description | Checks what route the IP traffic takes. Why? To help you keep track of what route is used for certain traffic. You can use the plugin to see what internet connection your traffic is using at the moment. How? By analysing the results from a trace made with the command traceroute. |
Categories | Networking |
Support Level | Level 4 (high and fully supported) |
Tags | route, traceroute, network |
check_rpc
Commands | check_rpc |
Description | Checks if an RPC service is registered and running. Why? To check the status of your RPC services. How? Connects to a real server and reports connection status. |
Supported platforms | |
Categories | Misc |
Support Level | Level 4 (high and fully supported) |
Tags | rpc service, unix, real |
check_sensors
Commands | check_sensors |
Description | Checks hardware status. Why? Gives you a knowledge of the hardware status, temperature, and so on. How? Checks status of your local hardware using the lm-sensors package. |
Supported platforms | with lm-sensors installed |
Categories | Hardware |
Support Level | Level 4 (high and fully supported) |
Tags | lmsensor, hardware, temperature, unix, linux |
check_simap
Commands | check_simap |
Description | Tests SIMAP connections with the specified host (or Why? To monitor the status of an IMAP mail server. How? Connects to a secure IMAP server and checks the status. |
socket).
Supported platforms | Not platform dependent |
Categories | |
Support Level | Level 5 (medium and bug support) |
Tags | email, imap, secure imap, tcp |
check_sip
Commands | check_sip |
Description | Tests the functionality of a SIP server. Why? To check that extensions are working as expected on your SIP server. How? The plugin makes a call to the specified extension on the SIP server to ensure that it is working, and returns the response time. |
Supported platforms | SIP servers |
Categories | Misc |
Support Level | Level 5 (medium and bug support) |
Tags | sip, asterisk |
check_sitescanner
Commands | check_sitescanner |
Description | Checks and returns the status of Site Scanner sensors and reports back the current status. Requires a Site Scanner account. Why? To integrate your Site Scanner monitoring into OP5 Monitor. How? The plugin contacts the simplified sensor status interface to get the status of the sensor with the specified SensorID. |
Supported platforms | Site Scanner accounts |
Categories | Network, web |
Support Level | Level 6 (low and best effort) |
Tags | web, sitescanner, network |
check_smsd
Commands | check_smsd |
Description | This plugin is used to monitor the number of failed SMS messages on an OP5 Monitor server. Why? To receive notifications when there are too many failed SMSs on your server. How? By checking the number of files in your smsd spool error directory. |
Supported platforms | OP5 Monitor or any other host running smsd |
Categories | Misc |
Support Level | Level 4 (high and fully supported) |
Tags | sms, gsm, sms spool queue |
check_smtp
Commands | check_smtp, check_smtp_time |
Description | Checks status of an SMTP server. Why? To see the status of your SMTP mail server. How? Connects to am SMTP server and checks the status. Allows you to specify expected response string. You can also run commands and specify thresholds on response times. |
Supported platforms | Not platform dependent |
Categories | |
Support Level | Level 4 (high and fully supported) |
Tags | email, smtp |
check_snmp
Commands | check_extreme_cpu (extreme snmp), check_extreme_power (extreme snmp), check_extreme_temperature (extreme snmp), check_hp_cpu (hp snmp), check_hp_fan (hp snmp), check_hp_fibre_array_status (hp snmp), check_hp_memoryfree (hp snmp), check_hp_nic_status (hp snmp), check_hp_power (hp snmp), check_hp_power_supply_condition (hp snmp), check_hp_raid_ctrl_status (hp snmp), check_hp_temperature (hp snmp), check_ibm_3584_media_access_availability (ibm 3584 snmp), check_ibm_3584_nr_of_physichal_medias (ibm 3584 snmp), check_ibm_3584_security_breach (ibm 3584 snmp), check_ibm_3584_status_of_mediaaccessdevice (ibm 3584 snmp), check_ibm_3584_storage_library_status (ibm 3584 snmp), check_ibm_raidstatus (ibm raid status snmp), check_netbotz_airflow (netbotz snmp), check_netbotz_door (netbotz snmp), check_netbotz_humidity (netbotz snmp), check_netbotz_motion_detection (netbotz snmp), check_netbotz_temp (netbotz snmp), check_snmp (generic snmp), check_snmp_apc_ups_batterystatus (ups apc snmp), check_snmp_apc_ups_batterytime (ups apc snmp), check_snmp_apc_ups_minremain (ups apc snmp), check_snmp_apc_ups_percentload (ups apc snmp), check_snmp_apc_ups_temp (ups apc snmp), check_snmp_cisco_cpu (cisco snmp), check_snmp_cisco_mem (cisco snmp), check_snmp_em1_humidity (environment probe em1 snmp), check_snmp_em1_temperature (environment probe em1 snmp), check_snmp_em1_wetness (environment probe em1 snmp), check_snmp_ipso_chassitemp (ipso hardware snmp), check_snmp_ipso_cpuload (ipso hardware snmp), check_snmp_ipso_fanstatus (ipso hardware snmp), check_snmp_ipso_powersupplystatus (ipso hardware snmp), check_snmp_ipso_powersupplytemp (ipso hardware snmp), check_snmp_netapp_cpu (netapp hardware snmp), check_snmp_netapp_failed_disk (netapp hardware snmp), check_snmp_netapp_fans (netapp hardware snmp), check_snmp_netapp_power (netapp hardware snmp), check_snmp_netapp_temperature (netapp hardware snmp), check_snmp_sicon_ups_batteryremain (sicon ups snmp), check_snmp_sicon_ups_involtage (sicon ups snmp), check_snmp_sicon_ups_outvoltage (sicon ups snmp), check_snmp_sysinfo (system information snmp), check_snmp_ups_batterysec (ups snmp), check_snmp_ups_batterystatus (ups snmp), check_snmp_ups_minremain (ups snmp), check_snmp_ups_percentload (ups snmp), check_snmp_ups_temp (ups snmp), check_snmp_v2c, check_snmp_v3 |
Description | Checks devices that support SNMP. Why? To get the status of devices that support SNMP. How? Obtains the status using the SNMP protocol. The plugin supports version 1, 2c, and 3. You need to specify version, community, or username/password and OID to poll. You can set thresholds on numeric ranges or match for specific strings. This is a very flexible plugin and can be used for almost anything with SNMP support. |
Supported platforms | Not platform dependent |
Categories | SNMP |
Support Level | Level 4 (high and fully supported) |
Tags | snmp |
check_snmp_boostedge
Commands | check_snmp_boostedge |
Description | Checks the BOOSTedge web accelerator. Why? To control the overall states of your BOOSTedge web accelerator. How? By SNMP |
Supported platforms | BOOSTedge web accelerators |
Categories | SNMP, misc, BOOSTedge, web accelerator, SNMP, network |
Support Level | Level 5 (medium and bug support) |
Tags | web, accelerator, network, boostedge, snmp |
check_snmp_cpfw
Commands | check_snmp_cpfw |
Description |
Checks Check Point FireWall-1 status and policy state (must be installed).
How? Checks by SNMP some modules of Check Point FireWall-1 filtering or management module. Each module is checked independently. |
Supported platforms | Check Point FireWall-1 |
Categories | SNMP, networking |
Support Level | Level 5 (medium and bug support) |
Tags | firewall-1, status, policy state, snmp, network |
check_snmp_css
Commands | check_snmp_css |
Description | Checks Cisco content switch Why? To make sure the services on your Cisco content switch work as expected. How? By SNMP. |
Supported platforms | Cisco content switch |
Categories | SNMP, networking |
Support Level | Level 5 (medium and bug support) |
Tags | cisco, css, network, snmp |
check_snmp_env
Commands | check_snmp_env |
Description | Checks environmental parameters such as fan, power supply, temperature on the following types of hosts: Cisco, Nokia IPSO, Blue Coat, IronPort, Foundry. Not all parameters are supported on every type of host. Why? To control the hardware in your network units. How? By SNMP. |
Supported platforms | Cisco, Nokia IPSO, Blue Coat, IronPort, Foundry |
Categories | SNMP, networking |
Support Level | Level 5 (medium and bug support) |
Tags | switch, router, cisco, nokia, bluecoat, ironport, foundry, environment, fan, power, temperature, snmp, network |
check_snmp_int
Commands | check_snmp_int |
Description | The plugin checks host interface state and usage. Why? To receive a notification if you suddenly have strange traffic patterns in you network, for example, indicating a possible virus attack, or to help you locate network problems. How? Checks an interface's operational status over SNMP using the mib-ii table. |
Supported platforms | Not platform dependent |
Categories | SNMP, networking |
Support Level | Level 5 (medium and bug support) |
Tags | network interface, status, snmp |
check_snmp_linkproof_nhr
Commands | check_snmp_linkproof_nhr |
Description | Checks Radware LinkProof and NHR Why? To ensure the balancing between routers in a multihomed environment is working as expected. How? By SNMP. |
Supported platforms | Radware LinkProof, NHR. |
Categories | SNMP, networking |
Support Level | Level 5 (medium and bug support) |
Tags | radware, linkproof nhr, snmp, network |
check_snmp_load
Commands | check_snmp_win_load, check_snmp_load |
Description | Checks CPU or load average on a number of different platforms. Why? This can be useful to monitor CPU or load average on hosts where you are not able to install any agents. How? By SNMP. |
Supported platforms | Cisco, Cisco Catalyst, HP ProCurve, LinkProof, Blue Coat, Nokia, Fortinet, NetScreen | , / , AS400,
Categories | CPU, SNMP |
Support Level | Level 5 (medium and bug support) |
Tags | cpu, load, snmp, microsoft windows, unix, linux, cisco, hp, linkproof, nokia, net screen, fortinet, blucoat, as400 |
check_snmp_mem
Commands | check_snmp_mem |
Description | Checks memory usage on a number of different platforms using SNMP. Why? Can be useful to monitor memory usage on hosts where you are not able to install any agents. How? Using Net-SNMP on for memory and swap usage; memory usage on Cisco routers, PIX, and HP ProCurve switches. On Cisco routers, it also checks IO and processor memory. On PIX, it checks the memory used (one memory pool only on PIX). |
Supported platforms | Cisco routers, Cisco PIX, HP ProCurve switch. | / ,
Categories | SNMP, memory |
Support Level | Level 5 (medium and bug support) |
Tags | memory, ciso pix, unix, linux, hp, snmp |
check_snmp_nsbox
Commands | check_snmp_nsbox |
Description | Checks vhost and diode status on your NetSecureOne NetBox. Why? To ensure the status of the diodes and vhosts are ok. How? By SNMP. |
Supported platforms | NetSecureOne NetBox |
Categories | SNMP |
Support Level | Level 5 (medium and bug support) |
Tags | netsecureone, netbox, vhost, diod status, snmp |
check_snmp_printer
Commands | check_snmp_printer |
Description | Checks printers by SNMP. Why? To check the status of printers. How? Connects by SNMP to the printers and checks their paper trays and toner level statuses. |
Supported platforms | Printers that support RFC 1759. |
Categories | SNMP |
Support Level | Level 5 (medium and bug support) |
Tags | printer, toner, paper, rcf1759, snmp |
check_snmp_process
Commands | check_snmp_process |
Description | Checks if processes are running, the number that are running, memory, and CPU used. How? The plugin checks, by SNMP, if there is at least one process matching the filter when no warning or critical levels are set. The filter is treated as a regular expression by default, but you can deactivate this. |
Supported platforms | , / , AS400 |
Categories | SNMP |
Support Level | Level 5 (medium and bug support) |
Tags | process, memory, cpu, microsoft windows, unix, linux, as400 |
check_snmp_storage
Commands | check_snmp_win_storage, check_snmp_win_virtual_mem, check_snmp_win_physical_mem, check_snmp_storage |
Description | Checks storage information on both hard drives and RAM on various hardware, using SNMP. Why? To monitor storage usage over SNMP, if SNMP is the only way to monitor the server. How? Collects the monitored data over SNMP. |
Supported platforms | Not platform dependent |
Categories | SNMP, file system |
Support Level | Level 5 (medium and bug support) |
Tags | storage, hardware, snmp |
check_snmp_vrrp
Commands | check_snmp_vrrp |
Description |
Checks the interface state of a VRRP cluster. |
Supported platforms | Nokia IP with IPSO 3.x and 4.x in both VRRP mode and clustering mode, Radware LinkProof, Alteon AD4 load balancers. |
Categories | SNMP, networking |
Support Level | Level 5 (medium and bug support) |
Tags | nokia, ipso, radware, alteon, loadbalancer, vrrp, cluster, snmp |
check_snmp_win
Commands | check_snmp_win |
Description | Used to monitor Why? Sometimes you are unable to install an agent on the monitored server. Setting up all SNMP services manually is a lot of work. This plugin does that for you. How? The monitored data is checked over SNMP. |
servers over SNMP instead of using an agent.
Supported platforms | |
Categories | |
Support Level | Level 5 (medium and bug support) |
Tags | microsoft windows, cpu, memory, snmp, os |
check_snmpif
Commands | check_snmpif_traffic_v1, check_snmpif_traffic_v2, check_snmpif_traffic_v3, check_snmpif_errors_v1, check_snmpif_errors_v2, check_snmpif_errors_v3, check_snmpif_status_v1, check_snmpif_status_v2, check_snmpif_status_v3, check_traffic, check_traffic_v2, check_traffic_v3, check_traffic_snmpport, check_traffic_v2_snmpport, check_traffic_v3_snmpport, check_iferrors, check_iferrors_v2, check_iferrors_v3, check_iferrors_snmpport, check_iferrors_v2_snmpport, check_iferrors_v3_snmpport, check_ifoperstatus, check_ifoperstatus_v2, check_ifoperstatus_v3 |
Description | Checks interface traffic, status, and errors using SNMP. Why? To be notified if, for example, you suddenly have strange patterns on your network, which may indicate a virus attack. How? Polls traffic, status, and error usage on an SNMP enabled network device, for example a router or a switch. The plugin allows you to specify threshold values. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support Level | Level 4 (high and fully supported) |
Tags | network, traffic, interface status, errors, snmp |
check_spop
Commands | check_spop |
Description | Checks the status of a POP3 server. Why? To check the status of your secure POP3 server. How? Connects to a secure POP3 server and checks the status. |
Supported platforms | Not platform dependent |
Categories | |
Support Level | Level 4 (high and fully supported) |
Tags | email, secure pop, tcp |
check_sql
Commands | check_mssql_backup_job, check_mssql_query_string_regex, check_mssql_query_count, check_mssql_query_reponstime, check_mssql_blocked_processes, check_mssql_backup_job_ad_user, check_mssql_query_string_regex_ad_user, check_mssql_query_count_ad_user, check_mssql_query_reponstime_ad_user, check_mssql_blocked_processes_ad_user |
Description | Checks various SQL servers. Requires DBI module for selected databases. Why? You can use this plugin to check a lot of different databases such as MySQL, Postgresql, SQL Server, and Db2. This plugin makes it easy to execute any kind of SQL query on the monitored database. How? It connects to the database using the database type specific dbi module. |
Supported platforms | Any database you can find Perl DBI modules for. |
Categories | Databases |
Support Level | Level 4 (high and fully supported) |
Tags | mysql, postgresql, microsoft sql, db2, dbi, database |
check_ssh
Commands | check_ssh, check_ssh_10, check_ssh_5 |
Description | Checks an SSH server. Why? Checks the status of your SSH servers. How? Connects to an SSH server and checks for an expected response. Allows you to specify what version to check for and also set thresholds on response time. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support Level | Level 4 (high and fully supported) |
Tags | ssh, ssh connection, tcp |
check_ssmtp
Commands | check_ssmtp |
Description | Checks status of a secure SMTP server. Why? To monitor the status of your secure SMTP mail server. How? Connects to a secure SMTP server and checks the status. Allows you to specify an expected response string. You can also run a command and specify thresholds on response time. |
Supported platforms | Not platform dependent |
Categories | |
Support Level | Level 4 (high and fully supported) |
Tags | email, smtp, secure smtp, tcp |
check_swap
Commands | check_swap |
Description | Checks swap usage. Why? To ensure sure you are notified if the server is using too much swap space. How? The swap is checked on the local machine. How this is done depends on what operating system the plugin is executed on. |
Supported platforms | / |
Categories | File system |
Support Level | Level 4 (high and fully supported) |
Tags | operating system, os, unix, linux, swap, memory |
check_tcp
Commands | check-host-alive-http (host alive over tcp 80), check-host-alive-telnet (host alive over tcp 23), check_imap3, check_imaps, check_tcp (general tcp port), check_telnet (telnet port) |
Description | Tests connection to a TCP port. Why? Checks the status of different applications that are listening on a TCP port. How? Connects to a specified TCP port and checks the connection. Lets you specify a port number, send and expect a string and also set thresholds on response time. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support Level | Level 4 (high and fully supported) |
Tags | tcp, network, port |
check_temptraxe
Commands | check_temptracker_e, check_temptrax_e4_probe |
Description | Check temperatures of a probe connected to a TempTrax Model E. Why? To be notified when temperatures in, for example, server rooms rises above defined thresholds. How? The plugin queries the status of TempTrax using HTTP protocol. |
Supported platforms | TempTrax Model E |
Categories | Environmental |
Support Level | Level 5 (medium and bug support) |
Tags | environment, temperature, temptrax model e |
check_temptraxf
Commands | check_temptraxf |
Description | Checks the temperature of a probe connected to a TempTrax Model F. Why? To be notified when the temperatures in, for example, server rooms rise above defined thresholds. How? Queries the status of TempTrax using HTTP protocol. |
Supported platforms | TempTrax Model F |
Categories | Environmental |
Support Level | Level 5 (medium and bug support) |
Tags | environment, temperature, temptrax model f |
check_time
Commands | check_time |
Description | Checks the time on a host running timeserver. Why? To check that the time is correct on remote systems. How? Connect to a host that is running timeserver on port 37. Allow you to set the accepted variance between the remote host and the local clock. |
Supported platforms | Not platform dependent |
Categories | Misc |
Support Level | Level 4 (high and fully supported) |
Tags | time, ntp, timeserver |
check_traffic
Commands | check_traffic |
Description | Checks the amount of traffic on a network port. Why? To be notified if, for example, you suddenly have strange traffic patterns in you network, indicating a possible virus attack. How? Polls traffic usage on an SNMP enabled network device, for example, a router or a switch. The plugin allows you specify to threshold values for traffic usage. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support Level | Level 4 (high and fully supported) |
Tags | network, snmp, router, switch |
check_ucs
Commands | check_ucs_temp, check_ucs_fan_status, check_ucs_iocard_status, check_ucs_psu_status, check_ucs_fault_summary |
Description | Checks the status of a Cisco UCS Blade chassis. Why? To check the status of chassis temperature, chassis fan status, chassis power supply status, IO card status, and fault summary from UCS Manager. How? Queries a remote machine over SNMP v2c using PerlNet. You need to you have SNMP read access on the Cisco UCS system you want to monitor. |
Supported platforms | Cisco UCS Blade systems |
Categories | Hardware |
Support Level | Level 6 (low and best effort) |
Tags | cisco ucs, hardware, powersupply, fan, snmp, blade system, temperature, ucs manager |
check_udp
Commands | check_udp |
Description | Tests connection to a UDP port. Why? To check the status of applications that listen on a UDP port. How? Connects to a specified UDP port and checks the connection. Allows you to specify port number, send and expect string and also to set thresholds on response time. |
Supported platforms | Not platform dependent |
Categories | Networking |
Support Level | Level 4 (high and fully supported) |
Tags | network, udp |
check_unix
Commands | check_unix |
Description | An OP5 Monitor plugin that checks a remote host through SSH or another
remote shell. Why? To automatically monitor the status of your UPSs and be notified in case of an outage. How? Checks status on UPSs. You can check battery status, temperature, and battery load, among other things. |
Supported platforms | UPS with RFC1628 SNMP support |
Categories | Operating systems |
Support Level | Level 6 (low and best effort) |
Tags | linux, unix, ssh, remote shell |
check_ups
Commands | check_ups |
Description | Checks SNMP enabled UPSs Why? To automatically monitor the status of your UPSs and be notified in case of an outage. How? Checks status on UPSs. You can check battery status, temperature, and battery load, among other things. |
Supported platforms | UPS with RFC1628 SNMP support |
Categories | Hardware |
Support Level | Level 5 (medium and bug support) |
Tags | ups, rfc1628, snmp, hardware |
check_users
Commands | check_users |
Description | Checks the number of logged-in users. Why? To keep track of the number of users logged on to a system. if too many are logged on, it could be a sign your system was hacked, for example. How? Checks for the number of users that are logged on to the system, with threshold values indicating the acceptable number. |
Supported platforms | |
Categories | Misc |
Support Level | Level 4 (high and fully supported) |
Tags | linux, unix, users, logged in |
urlize
Commands | check_log_eventlog, check_log_snmptraps, check_log_syslog |
Description | Creates a URL from a status message from another plugin. Why? To have a clickable URL in your status message in your OP5 Monitor status view. How? Wraps the text output of another command (plugin) in HTML tags, displaying the plugin output in as a clickable link in the status screen. The return status is the same as the invoked plugin. |
Supported platforms | Not platform dependent |
Categories | Misc |
Support Level | Level 4 (high and fully supported) |
Tags | url status message
|
check_vmware_api
Commands | check_vmware_api_dc, check_vmware_api_dc_host, check_vmware_api_dc_host_cpu_total_no_thresholds, check_vmware_api_dc_host_cpu_usage_in_mhz, check_vmware_api_dc_host_disk_io_aborted, check_vmware_api_dc_host_disk_io_device, check_vmware_api_dc_host_disk_io_kernel, check_vmware_api_dc_host_disk_io_queue, check_vmware_api_dc_host_disk_io_resets, check_vmware_api_dc_host_disk_io_total_no_thresholds, check_vmware_api_dc_host_mem_memctl_in_mb, check_vmware_api_dc_host_mem_overall_in_mb, check_vmware_api_dc_host_mem_overhead_in_mb, check_vmware_api_dc_host_mem_swap_in_mb, check_vmware_api_dc_host_mem_total_no_thresholds, check_vmware_api_dc_host_mem_usage_in_mb, check_vmware_api_dc_host_net_usage_receive, check_vmware_api_dc_host_net_usage_send, check_vmware_api_dc_host_net_usage_total_no_thresholds, check_vmware_api_dc_host_runtime_all_info, check_vmware_api_dc_host_runtime_connection_state, check_vmware_api_dc_host_runtime_health, check_vmware_api_dc_host_runtime_listcluster, check_vmware_api_dc_host_runtime_listhost, check_vmware_api_dc_host_runtime_listvm, check_vmware_api_dc_host_runtime_state, check_vmware_api_dc_host_runtime_vmware_tools_status, check_vmware_api_dc_host_scsi_logical_units, check_vmware_api_dc_host_vmfs_free, check_vmware_api_dc_host_vmfs_used, check_vmware_api_dc_host_vm_list, check_vmware_api_dc_vm, check_vmware_api_dc_vm_connection_state, check_vmware_api_dc_vm_cpu_all_no_thresholds, check_vmware_api_dc_vm_cpu_ready, check_vmware_api_dc_vm_cpu_usage, check_vmware_api_dc_vm_cpu_usage_mhz, check_vmware_api_dc_vm_cpu_wait, check_vmware_api_dc_vm_mem_active, check_vmware_api_dc_vm_mem_all_no_thresholds, check_vmware_api_dc_vm_mem_memctl, check_vmware_api_dc_vm_mem_overall, check_vmware_api_dc_vm_mem_overhead, check_vmware_api_dc_vm_mem_swap_in, check_vmware_api_dc_vm_mem_swap_out, check_vmware_api_dc_vm_mem_usage, check_vmware_api_dc_vm_mem_usage_mb, check_vmware_api_dc_vm_net_all_no_thresholds, check_vmware_api_dc_vm_net_receive, check_vmware_api_dc_vm_net_send, check_vmware_api_dc_vm_net_usage, check_vmware_api_dc_vm_runtime_all_info, check_vmware_api_dc_vm_runtime_console_connections, check_vmware_api_dc_vm_runtime_cpu, check_vmware_api_dc_vm_runtime_guest_os_status, check_vmware_api_dc_vm_runtime_issues, check_vmware_api_dc_vm_runtime_mem, check_vmware_api_dc_vm_runtime_state, check_vmware_api_dc_vm_runtime_status, check_vmware_api_dc_vm_runtime_vmware_tools_status, check_vmware_api_dc_vm_swap_usage, check_vmware_api_host, check_vmware_api_host_cpu_total_no_thresholds, check_vmware_api_host_cpu_usage, check_vmware_api_host_cpu_usage_in_mhz, check_vmware_api_host_disk_io_aborted, check_vmware_api_host_disk_io_device, check_vmware_api_host_disk_io_kernel, check_vmware_api_host_disk_io_queue, check_vmware_api_host_disk_io_read, check_vmware_api_host_disk_io_resets, check_vmware_api_host_disk_io_total_no_thresholds, check_vmware_api_host_disk_io_write, check_vmware_api_host_io_read, check_vmware_api_host_io_write, check_vmware_api_host_mem_memctl_in_mb, check_vmware_api_host_mem_overall_in_mb, check_vmware_api_host_mem_overhead_in_mb, check_vmware_api_host_mem_swap_in_mb, check_vmware_api_host_mem_total_no_thresholds, check_vmware_api_host_mem_usage, check_vmware_api_host_mem_usage_in_mb, check_vmware_api_host_net_nics, check_vmware_api_host_net_usage, check_vmware_api_host_net_usage_receive, check_vmware_api_host_net_usage_send, check_vmware_api_host_net_usage_total_no_thresholds, check_vmware_api_host_runtime_all_info_no_thresholds, check_vmware_api_host_runtime_connection_state_no_thresholds, check_vmware_api_host_runtime_health, check_vmware_api_host_runtime_issues, check_vmware_api_host_runtime_listvm, check_vmware_api_host_runtime_maintenance, check_vmware_api_host_runtime_sensor, check_vmware_api_host_runtime_status, check_vmware_api_host_runtime_storagehealth, check_vmware_api_host_service_all, check_vmware_api_host_service_specific, check_vmware_api_host_swap_usage, check_vmware_api_host_uptime, check_vmware_api_host_vm, check_vmware_api_host_vmfs, check_vmware_api_host_vmfs_used, check_vmware_api_host_vm_connection_state, check_vmware_api_host_vm_cpu_all_no_thresholds, check_vmware_api_host_vm_cpu_ready, check_vmware_api_host_vm_cpu_usage, check_vmware_api_host_vm_cpu_usage_mhz, check_vmware_api_host_vm_cpu_wait, check_vmware_api_host_vm_mem_active, check_vmware_api_host_vm_mem_all_no_thresholds, check_vmware_api_host_vm_mem_memctl, check_vmware_api_host_vm_mem_overall, check_vmware_api_host_vm_mem_overhead, check_vmware_api_host_vm_mem_swap_in, check_vmware_api_host_vm_mem_swap_out, check_vmware_api_host_vm_mem_usage, check_vmware_api_host_vm_mem_usage_mb, check_vmware_api_host_vm_net_all_no_thresholds, check_vmware_api_host_vm_net_receive, check_vmware_api_host_vm_net_send, check_vmware_api_host_vm_net_usage, check_vmware_api_host_vm_runtime_all_info, check_vmware_api_host_vm_runtime_console_connections, check_vmware_api_host_vm_runtime_cpu, check_vmware_api_host_vm_runtime_guest_os_status, check_vmware_api_host_vm_runtime_issues, check_vmware_api_host_vm_runtime_mem, check_vmware_api_host_vm_runtime_state, check_vmware_api_host_vm_runtime_status, check_vmware_api_host_vm_runtime_vmware_tools_status, check_vmware_api_host_vm_swap_usage |
Description | Checks the status of VMware ESX 3.x, ESXi server, vSphere 4 and vSphere 5. Why? Checks the status (CPU, memory, runtime, and others) of virtual machines running inside VMware ESX server, VMware ESX hosts, and vSphere infrastructure. How? Queries the status of ESX server or vSphere using the vi(vSphere) Perl API. |
Supported platforms | VMware ESX server, VMware ESXi server, VMware vSphere infrastructure |
Categories | Operating systems |
Support Level | Level 8 (deprecated)
This plugin has been deprecated in favor of check_vmware_v2. |
Tags | vmware, vsphere, vcenter, esx, esxi, data center |
check_vmware_v2
Commands | check_vmware_v2_esxi_host, check_vmware_v2_esxi_host_no_ssl, check_vmware_v2_vcenter_host, check_vmware_v2_vcenter_host_no_ssl, check_vmware_v2_vcenter_vm, check_vmware_v2_vcenter_vm_no_ssl check_vmware_v2_vcenter_cluster, check_vmware_v2_vcenter_cluster_no_ssl, check_vmware_v2_vcenter_datacenter, check_vmware_v2_vcenter_datacenter_no_ssl |
Description | Checks the status of VMware vSphere infrastructure. Why? The plugin can be used to monitor the infrastructure managed by a VMware vCenter server or a VMware ESXi server, such as its data centres, clusters, hosts, and virtual machines. It can check a large range of different metrics and statuses, depending on the targeted infrastructure; for example CPU load, memory usage, network activity, and runtime states. How? The plugin requires a separate service to run on the OP5 Monitor host. The plugin talks to the service which in turn talks to the target vSphere API server. The plugin service uses the pyVmomi vSphere API Python bindings from VMware to talk to the VMware vSphere infrastructure. |
Supported platforms | VMware vSphere infrastructure: VMware vCenter and VMware ESX and ESXi hypervisor hosts.
The plugin uses pyVmomi 6.7.1, which means that it fully supports vSphere 6.7.1, 6.7, 6.5 and 6.0. |
Categories | Operating systems |
Support Level | Level 5 (medium and bug support) |
Tags | vmware, vsphere, vcenter, esx, esxi |
check_wave
Commands | check_wave |
Description | Tests signal strength on SpeedLan wireless equipment. Why? To ensure you are notified if the signal strength is not as expected. How? Using SNMP. |
Supported platforms | SpeedLan wireless equipment |
Categories | Networking |
Support Level | Level 6 (low and best effort) |
Tags | speedlan, wlan, snmp |
check_wmi_plus
Commands | check_wmip, check_wmip_io, check_wmip_filesize, check_wmip_fileage, check_wmip_disk, check_wmip_cpuq, check_wmip_cpu, check_wmip_cpudetail, check_wmip_network, check_wmip_service, check_wmip_uptime, check_wmip_mem, check_wmip_page, check_wmip_process, check_wmip_eventlog, check_wmip_ts, check_wmip_iis, check_wmip_exchange, check_wmip_sql, check_wmip_sql_express, check_wmip_proc, check_wmip_dns, check_wmip_dhcp, check_wmip_dhcpv6, check_wmip_print, check_wmip_users, check_wmip_power, check_wmip_ad |
Description | Checks the status of How? The plugin queries the status of servers using the WMI API. |
servers using WMI (agent-less).
Supported platforms | |
Categories | Operating systems |
Support Level | Level 5 (medium and bug support) |
Tags | microsoft windows, wmi, agent less, os |
check_xenapi
Commands | check_xenapi_list_host, check_xenapi_list_pool, check_xenapi_list_vms, check_xenapi_host_cpu, check_xenapi_host_cpu_core, check_xenapi_host_io, check_xenapi_host_mem, check_xenapi_host_net, check_xenapi_host_time, check_xenapi_vm_cpu, check_xenapi_vm_io, check_xenapi_vm_mem, check_xenapi_vm_mem_ballooned, check_xenapi_vm_nets |
Description | Checks the status of a Citrix XenServer cluster installation. Why? Checks the status (for example CPU, memory, disk IO) of virtual machines running inside Citrix XEN server clusters and the hosts themselves. How? The plugin queries status of Citrix XenServer clusters using the Xen API. |
Supported platforms | Citrix XenServer |
Categories | Operating systems |
Support Level | Level 4 (high and fully supported) |
Tags | xen, citrix, os |
check_yum_update
Commands | check_yum_update |
Description | Checks for available updates using the command yum check-updates. Why? To ensure sure you do not miss important updates on any Red Hat or system that uses yum as a package manager. How? Uses the yum command to get the number of new packages available for installation. |
Supported platforms | Red Hat, , |
Categories | Misc |
Support Level | Level 4 (high and fully supported) |
Tags | yum, os updates, redhat, centos |
webinject
Commands | check_webinject |
Description |
Used to make complex web queries. |
Supported platforms | Not platform dependent |
Categories | Network, web |
Support Level | Level 4 (high and fully supported) |
Tags | web applications |