Advanced Nagios Plugins Collection
NoSQL, Hadoop, Redis, Cassandra, Elasticsearch, Solr, MySQL, Linux, HBase, MongoDB etc
450+ AWS, Hadoop, Cloud, Kafka, Docker, Elasticsearch, RabbitMQ, Redis, HBase, Solr, Cassandra, ZooKeeper, HDFS, Yarn, Hive, Presto, Drill, Impala, Consul, Spark, Jenkins, Travis CI, Git, MySQL, Linux, DNS, Whois, SSL Certs, Yum Security Updates, Kubernetes, Mesos, Riak, MongoDB, Memcached, Couchbase, CouchDB, Neo4j, Ambari, Cloudera, Hortonwork…
Advanced Nagios Plugins Collection
Largest, most advanced collection of production-grade Nagios monitoring code (over 450 programs).
Supports most major open source NoSQL technologies, Pub-Sub / Message Buses, CI, Web and Linux based infrastructure, including:
- Hadoop - extensive API integration to all major Hadoop vendors (Cloudera, Hortonworks, MapR, IBM BigInsights)
- Solr / SolrCloud
- Travis CI
- Linux - various including the widely used
check_yum.pyfor RHEL / CentOS yum security updates
- SSL Certificate expiry in days & validations
- Whois domain expiry in days & validations
- advanced DNS record checks (MX, NS, SRV etc)
- Git, MySQL ... etc.
Supports a a wide variety of compatible Enterprise Monitoring systems.
Most enterprise monitoring systems come with basic generic checks, while this project extends their monitoring capabilities significantly further in to advanced infrastructure, application layer, APIs etc.
If running against services in Cloud or Kubernetes, just target the load balancer address or the Kubernetes Service or Ingress addresses.
Also useful to be run on the command line for testing or in scripts for dependency availability checking, and comes with a selection of advanced HAProxy configurations for these technologies to make monitoring and scripting easier for clustered technologies.
Cloud & Big Data Contractor, United Kingdom
(you're welcome to connect with me on LinkedIn)
Make sure you run
make update if updating and not just
git pull as you will often need the latest library submodules and probably new upstream libraries too.
- Git clone this repo and compile dependencies by running
- Download pre-built self-contained Docker image
Execute each program on the command line with
--help to see its options.
Ready-to-run Docker Image
docker pull harisekhon/nagios-plugins
List all plugins:
docker run harisekhon/nagios-plugins
Run any given plugin by suffixing it to the
docker run command:
docker run harisekhon/nagios-plugins
docker run harisekhon/nagios-plugins check_ssl_cert.pl --help
There are also
:ubuntu tagged docker images available, as well as
:perl only images.
You should tag the build locally as
:stable or date-time stamped and run off that tag to avoid it getting auto-replaced by newer
:latest builds, to control updates to suit your schedule and prevent random delays from
docker runs pulling down newer builds from DockerHub.
Automated Build from Source
git clone https://github.com/harisekhon/nagios-plugins cd nagios-plugins make build zookeeper
Now run any plugin with
--help to find out which switches to use.
Make sure to read Detailed Build Instructions further down for more information.
Optional: Generate self-contained Perl scripts with all dependencies built in to each file for easy distribution
make build has finished, if you want to make self-contained versions of all the perl scripts with all dependencies included for copying around, run:
The self-contained scripts will be available in the
Quick Plugins Guide
There are over 400 programs in this repo so these are just some of the highlights.
- Hadoop Ecosystem - HDFS, Yarn, HBase, Ambari, Atlas, Ranger
- Service Discovery & Coordination - ZooKeeper, Consul, Vault
- Cloud - AWS
- Docker / Containerization - Docker & Docker Swarm, Mesos, Kubernetes
- Search - Elasticsearch, Solr / SolrCloud
- NoSQL - Cassandra, Redis, Riak, Memcached, CouchDB
- SQL Databases - MySQL
- Pub-Sub / Message Queues - Kafka, Redis, RabbitMQ
- CI - Continuous Integration & Build Systems - Jenkins, Travis CI, GoCD, DockerHub, Git
check_hadoop_*.pl/py- various Apache Hadoop monitoring utilities for HDFS, YARN and MapReduce (both MRv1 & MRv2):
- Hadoop - Masters' status and High Availability (ZKFC, Active/Standby state), Worker nodes counts, dead nodes / blacklisted / unhealthy nodes, heap usage, metrics and JMX information with optional thresholds & graph data
- HDFS - NameNode & DataNode checks, cluster space, balance, block replication, block count limits per datanode / cluster total, safe mode, failed name dirs, WebHDFS (with HDFS HA failover support), HttpFS, HDFS writeability, rack resilience configuration (checks more than 1 rack configured, finds nodes with default rack configured), HDFS fsck status / last check / run time / max blocks, HDFS file / directory existence & metadata attributes
- Infrastructure - Resource Manager and NodeManager checks, unhealthy NodeManagers, queue state, queue capacity, app stats, % of memory allocated, metrics with optional thresholds to check things such as activeNodes, appsPending, lostNodes, unhealthyNodes etc.
- Apps - app last finished state / user / queue / elapsed time (batch job SLAs), queue apps allowed/disallowed (catch Spark Shells on production queue), app running (check long living yarn service is still alive), long running apps/jobs detection with name and queue include/exclude regexes (detect SLAs breaches for in-progress batch jobs or forgotten Spark Shells holding resources, both Spark Scala and PySpark)
check_hbase_*.py/pl- various Apache HBase monitoring utilities using Thrift + Stargate APIs, checks Masters / Backup Masters, RegionServers, table availability (exists, is enabled, and has minimum number of column families), number of expected table regions, unassigned table regions, regions stuck in transition, region count balance across RegionServers, requests per sec balance across RegionServers, compaction in progress (by table and by regionserver), number of regions in transition, longest current region migration time, hbck status for any inconsistencies, cell content vs optional regex + thresholds, table write and read back of unique generated values with write/read/delete latency checks against all detected column families, table write spray and read back of unique values across all regions for all column families with write/read/delete latency checks, gather metrics
check_atlas_*.py- Apache Atlas metadata server instance status, as well as metadata entity checks including entity existence, state=ACTIVE, expected type, expected tags are assigned to entity (eg. PII - important because Ranger ACLs to allow or deny access to data can be assigned based on tags)
check_ranger_*.pl/.py- Apache Ranger checks:
- policy checks - existence, enabled, has auditing enabled, is recursive, last updated vs thresholds (to catch changes), repository name and type that the policy belongs to
- repository checks - existence, active, type (eg. hive, hdfs), last updated vs thresholds (to catch changes)
- number of policies and repositories vs thresholds
check_ambari_*.pl- Apache Ambari API checks for Hadoop clusters written running the standard open source Hortonworks distribution - checks the service status, node(s) status, stale configs, cluster alerts summary, host alerts summary, cluster health report, hdfs rack resilience configured (checks more than 1 rack configured, finds nodes with default rack configured), kerberos enabled, cluster version, service config compatible with stack and cluster
Attivio, Blue Talon, Datameer, Platfora, Zaloni plugins are also available for those proprietary products related to Hadoop.
check_cloudera_manager_*.pl- Hadoop cluster checks via Cloudera Manager API - checks states and health of cluster services/roles/nodes, management services, config staleness, Cloudera Enterprise license expiry, Cloudera Manager and CDH cluster versions, utility switches to list clusters/services/roles/nodes as well as list users and their role privileges, fetch a wealth of Hadoop & OS monitoring metrics from Cloudera Manager and compare to thresholds. Disclaimer: I worked for Cloudera, but seriously CM collects an impressive amount of metrics making check_cloudera_manager_metrics.pl alone a very versatile program from which to create hundreds of checks to flexibly alert on
- Hortonworks - the standard modern Hadoop distribution - see
check_ambari_*.plin the Hadoop Ecosystem section above
check_mapr*.pl- Hadoop cluster checks via MapR Control System API - checks services and nodes, MapR-FS space (cluster and per volume), volume states, volume block replication, volume snapshots and mirroring, MapR-FS per disk space utilization on nodes, failed disks, CLDB heartbeats, MapR alarms, MapReduce mode and memory utilization, disk and role balancer metrics. These are noticeably faster than running equivalent maprcli commands (exceptions: disk/role balancer use maprcli).
check_ibm_biginsights_*.pl- Hadoop cluster checks via IBM BigInsights Console API - checks services, nodes, agents, BigSheets workbook runs, dfs paths and properties, HDFS space and block replication, BI console version, BI console applications deployed
check_hiveserver2*- Apache Hive - HiveServer2 LLAP Interactive server status and uptime, peer count, check for a specific peer host fqdn via regex and a basic beeline connection trivial query test
check_apache_drill_*.py/.pl- Apache Drill checks:
- cluster wide: number of online / offline cluster nodes, mismatched versions across cluster
- per drill node: status, cluster membership, encryption enabled, config settings, storage plugins enabled, version, metrics with optional thresholds
check_presto_*.py- Presto SQL DB
- cluster checks (via coordinator API) - number of current queries, running/failed/blocked/queued queries, tasks, worker nodes, failed worker nodes, workers with response lag to coordinator, workers with recent failures and recent failure ratios vs thresholds, version
- per node checks - status, if coordinator, environment
- per worker checks (via coordinator API) - specific worker registered with coordinator, response age to coordinator, recent requests vs threshold, recent successes, recent failures & failure ratio vs thresholds
Service Discovery & Coordination
check_zookeeper.pl- Apache ZooKeeper server checks, multiple layers: "is ok" status, is writable (quorum), operating mode (leader/follower vs standalone), gather statistics
check_zookeeper_*znode*.pl- ZooKeeper znode checks using ZK Perl API, useful for HBase, Kafka, SolrCloud, Hadoop HDFS & Yarn HA (ZKFC) and any other ZooKeeper-based service. Very versatile with multiple optional checks including data vs regex, json field extraction, ephemeral status, child znodes, znode last modified age
check_consul_*.py- Consul API write / read back, arbitrary key-value content checks, cluster leader election, number of cluster peers, service leader election, version
check_vault_*.py- Hashicorp's Vault API checks - health checks is initialized, is not standby, is vault sealed / unsealed, time skew between Vault server and local, is high availability enabled, is current leader, is leader found, version
check_aws_s3_file.pl- check for the existence of any arbitrary file on AWS S3, eg. to check backups have happened or _SUCCESS placeholder files are present for a job
check_aws_access_keys_age.py- checks for AWS access key age greater than N days to delete/rotate old keys as per best practice (optionally only alerts for active keys)
check_aws_access_keys_disabled.py- checks for AWS disabled access keys that should be removed
check_aws_api_ping.py- simple yes/no check for AWS API access, can be used to test access key credentials and as a dependency check for all other AWS checks
check_aws_cloudtrails_enabled.py- checks Cloud Trails have logging enabled, multi-region and logfile validation. Optionally check only a single named cloud trail
check_aws_cloudtrails_event_selectors.py- checks Cloud Trails have at least one event selector each with management and read+write logging. Optionally check only a single named cloud trail
check_aws_ec2_instance_count.py- checks the number of running instances with optional range thresholds
check_aws_ec2_instance_states.py- checks the state of all EC2 instances, outputting totals and checking warning thresholds for each status type
check_aws_password_policy.py- checks the AWS password policy including minimum length, maximum age, password reuse count, uppercase/lowercase/numbers/symbols and whether users are allowed to change their passwords
check_aws_root_account.py- checks the AWS root account has MFA enabled and no access keys as per best practice
check_aws_user_last_used.py- checks if a given AWS IAM user account has been used within the last N days (eg. if root account was recently used this may indicate a security breach or is at the very least against best practice)
check_aws_users_unused.py- detects old AWS IAM user accounts that haven't been used in the last N days, either passwords nor access keys, and should probably be removed
check_aws_users_password_last_used.py- detects AWS IAM user accounts that haven't had their passwords used in N days and should probably be removed
check_aws_users_mfa_enabled.py- checks all AWS user accounts with passwords have MFA enabled
Docker / Containerization
check_docker_*.py- Docker API checks including API ping, counts of running / paused / stopped / total containers with thresholds, specific container status by name or id, images count with thresholds, specific image:tag availability including size and checksum, counts of networks / volumes with thresholds, docker engine version
check_docker_swarm_*.py- Docker Swarm API checks including is swarm enabled, swarm node status, is the node a swarm manager, swarm service status including number of live replicas / tasks and if the service was updated recently, counts of services, swarm manager and worker nodes with thresholds, swarm errors, swarm version
check_mesos_*.pl- Mesos master health API, master & slaves state information including leader and versions, activated & deactivated slaves, number of Chronos jobs, master & slave metrics. Warning: Mesos & Mesosphere DC/OS is legacy semi-proprietary - major momentum has shifted to the open source Kubernetes project
check_kubernetes_*.py- Kubernetes API health and version
If running docker checks from within the nagios plugins docker image then you will need to expose the socket within the container, like so:
docker run -v /var/run/docker.sock:/var/run/docker.sock harisekhon/nagios-plugins check_docker_images.py -H unix:///var/run/docker.sock OK: Docker images = 296 | docker_images=296;; query_time=0.1568s
See also DockerHub build status nagios plugin further down in the CI section.
check_elasticsearch_*.pl/.py- Elasticsearch cluster state, shards, replicas, number of nodes & data nodes online, shard and disk % balance between nodes, single node ok, specific node found in cluster state, slow tasks, pending tasks, elasticsearch / lucene versions, per index existence / shards / replicas / settings / age, stats per cluster / index / node, X-Pack license expiry and features enabled
check_logstash_*.py- Logstash status, uptime, hot threads, plugins, version, number of pipelines online, specific pipeline online and optionally its number of workers, if its dead letter queue is enabled, outputs pipeline batch size and delay
check_solr*.pl- checks for Apache Solr and SolrCloud including API write/read/delete, arbitrary Solr queries vs num matching documents, API ping, Solr Core Heap / Index Size / Number of Docs for a given Solr Collection, and thresholds in ms against all Solr API operations as well as perfdata for graphing, as well as SolrCloud ZooKeeper content checks for collection shards and replicas states, number of live nodes in SolrCloud cluster, overseer, SolrCloud config and Solr metrics.
check_datastax_opscenter_*.pl- Apache Cassandra and DataStax OpsCenter monitoring, including Cassandra cluster nodes, token balance, space, heap, keyspace replication settings, alerts, backups, best practice rule checks, DSE hadoop analytics service status and both nodetool and DataStax OpsCenter collected metrics
check_memcached_*.pl- Memcached API writes/reads/deletes with timings, check specific key's value against regex or value range, number of current connections, gather statistics
check_couchdb_*.py- Apache CouchDB API checks including server status, database exists, doc and deleted doc counts, data size, compaction running, version
check_riak_*.pl- Riak API writes/reads/deletes with timings, check a specific key's value against regex or value range, check all riak diagnostics, check node states, check all nodes agree on ring status, gather statistics, alert on any single stat
check_redis_*.pl- Redis API writes/reads/deletes with timings, check specific key's value against regex or value range, replication slaves I/O, replicated writes (write on master -> read from slave), publish/subscribe, connected clients, validate redis.conf against running server to check deployments or remote compliance checks, gather statistics, alert on any single stat
check_mysql_query.pl- flexible free-form MySQL SQL queries - can check almost anything - obsoleted a dozen custom MySQL plugins and prevented writing many more. Tested against many versions of MySQL and MariaDB. You may also be interested in Percona's plugins
check_mysql_config.pl- detect differences in your /etc/my.cnf and running MySQL config to catch DBAs making changes to running databases without saving to /etc/my.cnf or backporting to Puppet. Can also be used to remotely validate configuration compliance against a known good baseline. Tested against many versions of MySQL and MariaDB
Publish - Subscribe / Message Queues
These programs check these message brokers end-to-end via their API, by acting as both a producer and a consumer and checking that a unique generated message passes through the broker cluster and is received by the consumer at the other side successfully. They report the publish, consumer and total timings taken, against which thresholds can be applied, and are also available as perfdata for graphing.
check_kafka.py/.pl- Kafka brokers API write & read back with configurable topics/partition and producer behaviour for acks, sleep, retries, backoff, can also lists topics and partitions. See Kafka Scala Nagios Plugin for a version with Kerberos support
check_redis_publish_subscribe.pl- Redis publish-subscribe API write & read back with configurable subscriber wait. See other Redis checks under NoSQL
check_rabbitmq*.py- RabbitMQ brokers AMQP API write & read back with configurable vhost, exchange, exchange type, queue, routing key, durability, RabbitMQ 'confirms' protocol extension & standard AMQP transactions support. Checks via the RabbitMQ management API include aliveness queue health test, built-in health checks, cluster name, vhost, exchange with optional validation of exchange type (direct, fanout, headers, topic) and durability (true/false), user auth and permissions tags, stats db event queue
CI - Continuous Integration & Build Systems - Git, Jenkins, Travis CI & DockerHub Automated Builds
check_jenkins_*.py- Jenkins checks include job build status, color, health report score, build time, age since last completed build, if job is set to buildable, job count total or per view, number of running builds, queued builds, executors, node count, offline nodes, jenkins mode, is security enabled, if a given node is online and its number of executors, if a given plugin is enabled and if there are available plugin updates individually or overall, with perfdata for relevant metrics like build time, jobs/nodes/executors/plugins/plugin updates, running/queued build counts and query timings
check_travis_ci_last_build.py- Travis CI repo's last build status - includes showing build number, build duration with optional thresholds, start/stop date & time, if there are currently any builds in progress and perfdata for graphing last build time and number of builds in progress. Verbose mode gives the commit details as well such as commit id and message
check_gocd_*.py- GoCD server and agent health, pipeline, stage and job level status checks, and number of agents online, enabled, and in different states
check_dockerhub_repo_build_status.py- DockerHub Automated Build status check for a given DockerHub repository's latest build or latest build for a given tag. Returns status and tag of last build along with perfdata for graphing build latency (time between build creation and completion) and query timing. Optionally also returns in verbose mode what triggered the build (webhook, revision control change, API / website trigger), created and last updated date timestamps and build URL to investigate
check_git_*- checks a Git checkout is valid, up to date with upstream remote/origin, has no uncommitted changes (staged or unstaged), no untracked files, isn't dirty, is in the right branch, isn't remote, isn't detached, is / isn't bare. Useful for monitoring deployment servers running off Git checkouts (a common scenario for things like PuppetMasters, Ansible AWX / Tower etc) to ensure your automation is deploying the right thing and that any ad-hoc modifications and tests have been properly backported to Git
Infrastructure - Internet - Web, DNS, SSL, Domains
check_ssl_cert.pl- SSL certificate checker - checks certificate expiry (days), validates domain, chain of trust, SNI, wildcard domains, SAN certs with multi-domain support. Chain of Trust support is important when building your JKS or certificate bundles to include intermediate certs otherwise certain mobile devices don't validate the SSL even though it may work in your desktop browser
check_whois.pl- check domain expiry days left and registration details match expected
check_dns.pl- advanced DNS query checker supporting NS records for your public domain name, MX records for your mail servers, SOA, SRV, TXT as well as A and PTR records. Can optionally specify
--regexresults (which is anchored for security) for strict validation to ensure all records returned are expected and authorized. The record, type and result(s) are output along with the DNS query timing perfdata for graphing DNS performance
Infrastructure - Linux - OS, Network, Puppet, RAID, SSH, Clusters, Yum Security Updates
check_puppet.rb- thorough, find out when Puppet stops properly applying manifests, if it's in the right environment, if it's --disabled, right puppet version etc
check_disk_write.pl- canary write test, catches partitions getting auto-remounted read-only by Linux when it detects underlying storage I/O errors (often caused by malfunctioning block devices, raid arrays, failing disks), see also
check_linux_*.pl/.py- checks RAM used, CPU context switches, system file descriptors, interface errors / promiscous mode / duplex / speed / MTU / stats, load normalized per CPU core (more useful than the default check_load plugin which would need different configs for heterogenous hardware), timezone settings, users / groups present (eg. PAM/LDAP/SSSD integration is working), duplicate UID/GIDs (helps detects rogue uid 0 accounts and more common LDAP vs local id range overlap misconfigurations), check groups.allow contains only specific groups, huge pages are disabled (often recommended for Big Data and NoSQL systems such as Hadoop and MongoDB), any read-only filesystems (more of a sweep than
check_disk_write.pl, with include/exclude regex)
check_ssh_login.pl- performs a full SSH login with username & password, good for testing your Dell DRAC / HP iLO infrastructure is properly secured and accessible. Also works for your Linux servers and even Mac OSX
older/check_*raid.py- RAID controller / array checks for 3ware, LSI MegaRaid / Dell PERC controllers (they're rebranded from LSI), and Linux software MD Raid. I also recommend the widely used Dell OpenManage Check
check_*_version*.pl/.py- checks running versions of software - originally written to detect version inconsistencies across large clusters of servers and failed/partial upgrades across large automated infrastructures. Now also used to check Docker tagged images contain the right versions of the expected software (which double validates that other programs in this and other github repos have actually been tested against all the expected versions)
check_cluster_version.plcan be used to tie together versions returned from many different servers (by passing it their outputs via Nagios macros) to ensure a cluster is all running the same version of software even if you don't enforce a particular
--expectedversion on individual systems
check_yum.py/.pl- widely used yum security updates checker for RHEL 5 - 7 systems dating back to 2008. You'll find forks of this around including NagiosExchange but please re-unify on this central updated version. Also has a Perl version which is a newer straight port with nicer more concise code and better library backing as well as configurable self-timeout. For those running Debian-based systems like Ubuntu see
... and there are many more plugins than we have space to list here, have a browse!
This code base is under active development and there are many more cool plugins pending import.
See also other 3rd Party Nagios Plugins you might be interested in.
Compatibility / Translation Plugins
These allow you to use any standard nagios plugin with other non-Nagios style monitoring systems by prefixing the nagios plugin command with these programs, which will execute and translate the outputs:
adapter_csv.py- executes and translates output from any standard nagios plugin to CSV format
adapter_check_mk.py- executes and translates output from any standard nagios plugin to Check_MK local plugin format
adapter_geneos.py- executes and translates output from any standard nagios plugin to Geneos CSV format
All plugins come with
--help which lists all options as well as giving a program description, often including a detailed account of what is checked in the code. You can also find example commands in the
Environment variables are supported for convenience and also to hide credentials from being exposed in the process list eg.
$PASSWORD. These are indicated in the
--help descriptions in brackets next to each option and often have more specific overrides with higher precedence eg.
$ELASTICSEARCH_HOST takes priority over
$REDIS_PASSWORD takes priority over
Make sure to run the automated build or install the required Perl CPAN / Python PyPI modules first before calling
Kerberos Security Support
Perl HTTP Rest-based plugins have implicit Kerberos support via LWP as long as the LWP::Authen::Negotiate CPAN module is installed (part of the automated
make build). This will look for a valid TGT in the environment (
$KRB5CCNAME) and if found will use it for SPNego.
Most Python HTTP Rest-based plugins for technologies / APIs with authentication have a
--kerberos switch which supercedes
--username/--password and can be used on technologies that support SPNego Kerberos authentication. It will either use the TGT from the environment cache (
$KRB5CCNAME) or if
$KRB5_CLIENT_KTNAME is present will kinit from the keytab specified in
$KRB5_CLIENT_KTNAME to a unique path per plugin to prevent credential cache clashes if needing to use different credentials for different technologies.
Automating Kerberos Tickets - if running a plugin by hand for testing then you can initiate your TGT via the
kinit command before running the plugin but if running automatically in a monitoring server then use the standard
k5start kerberos utility as a service to auto-initiate and auto-renew your TGT so that your plugins always authenticate to Kerberized services with a current valid TGT.
To use different kerberos credentials per plugin you can
export KRB5CCNAME=/different/path before executing each plugin, and have multiple
k5start instances maintaining each one.
High Availability / Multi-Master testing
Testing high availability and multi-master setups is best done through a load balancer.
HAProxy configurations are provided for all the major technologies under the haproxy-configs/ directory for many of the technologies tested in this project, including:
- Hadoop HDFS NameNodes
- Hadoop Yarn Resource Managers
- HBase Masters, Stargate Rest & Thrift servers
- Apache Drill
- Presto SQL Coordinators
- Kubernetes API
The following is pulled from my DevOps Python Tools repo (currently one of my favourite repos):
find_active_server.py- returns the first available healthy server or determines the active master in high availability setups. Configurable tests include socket, http, https, ping, url with optional regex content match and is multi-threaded for speed. Useful for pre-determining a server to be passed to tools that only take a single
--hostargument but for which the technology has later added multi-master support or active-standby masters (eg. Hadoop, HBase) or where you want to query cluster wide information available from any online peer (eg. Elasticsearch, RabbitMQ clusters). This is downloaded from my DevOps Python Tools repo as part of the build and placed at the top level. It has the ability to extend any nagios plugin to support multiple hosts in a generic way if you don't have a front end load balancer to run the check through. Example usage:
./check_elasticsearch_cluster_status.pl --host $(./find_active_server.py --http --port 9200 node1 node2 node3)
There are now also simplified subclassed programs so you don't have to figure out the switches for more complex services like Hadoop and HBase, just provide hosts as simple arguments and they'll return the current active master!
These are especially useful for ad-hoc scripting or quick command line tests.
Configuration for Strict Domain / FQDN validation
Strict validations include host/domain/FQDNs using TLDs which are populated from the official IANA list. This is done via the Lib and PyLib submodules for Perl and Python plugins respectively - see those repos for details on configuring to permit custom TLDs like
.intranet (both already supported by default as they're quite common customizations).
Most of the plugins I've read from Nagios Exchange and Monitoring Exchange (now Icinga Exchange) in the last decade have not been of the quality required to run in production environments I've worked in (ever seen plugins written in Bash with little validation, or mere 200-300 line plugins without robust input/output validation and error handling, resulting in "UNKNOWN: (null)" when something goes wrong - right when you need them - then you know what I mean). That prompted me to write my own plugins whenever I had an idea or requirement.
That naturally evolved in to this, a relatively Advanced Collection of Nagios Plugins, especially when I began standardizing and reusing code between plugins and improving the quality of all those plugins while doing so.
- specific error messages to aid faster Root Cause Analysis
- consistent behaviour
- standardized switches
- strict input/output validation at all stages, written for security and robustness
- code reuse, especially for more complex input/output validations and error handling
--warning/--criticalthresholds with range support, in form of
@prefix inverts to expect value outside of this range)
- support for use of
$PASSWORDenvironment variables as well as more specific overrides (eg.
$REDIS_PASSWORD) to give administrators the option to avoid leaking
--passwordcredentials in the process list for all users to see
- Metrics Graphing integrations - Graphite, InfluxDB, OpenTSDB and PNP4Nagios can all auto-graph the perfdata from these plugins
- Continuous Integration with tests for success and failure scenarios:
- unit tests for the custom supporting perl and python libraries
- integration tests of the top level programs using the libraries for things like option parsing
- functional tests for the top level programs using Docker containers for each technology (eg. Cassandra, Elasticsearch, Hadoop, HBase, ZooKeeper, Memcached, Neo4j, MongoDB, MySQL, Riak, Redis...)
- easy rapid development of new high quality robust Nagios plugins with minimal lines of code
Several plugins have been merged together and replaced with symlinks to the unified plugins bookmarking their areas of functionality, similar to some plugins from the standard nagios plugins collection.
Some plugins such as those relating to Redis and Couchbase also have different modes and expose different options when called as different program names, so those symlinks are not just cosmetic. An example of this is write replication, which exposes extra options to read from a slave after writing to the master to check that replication is 100% working.
Perl ePN optimization is not supported at this time as I was running 13,000 production checks per Nagios server years ago (circa 2010) without ePN optimization - it's not worth the effort and isn't available in any of the other languages anyway.
Python plugins are all pre-byte-compiled as part of the automated build.
Modern scaling should be done using distributed computing, open source examples include Icinga2 and Shinken. Shinken's documentation cites an average 4 core server @ 3Ghz as supporting 150,000 checks per 5 minutes, which aligns with my own experience with Nagios Core. Using the latest hardware and proper setup could probably result in even higher scale before having to move to distributed monitoring architecture.
Having written a large number of Nagios Plugins in the last 10 years in a variety of languages (Python, Perl, Ruby, Bash, VBS) I abstracted out common components of a good robust Nagios Plugin program in to libraries of reusable components that I leverage very heavily in all my modern plugins and other programs found under my other repos here on GitHub, which are now mostly written in Perl or Python using these custom libraries, for reasons of both concise rapid development and speed of execution.
These libraries enables writing much more thoroughly validated production quality code, to achieve in a quick 200 lines of Perl or Python what might otherwise take 2000-3000 lines to do properly (including some of the more complicated supporting code such as robust validation functions with long complex regexs with unit tests, configurable self-timeouts, warning/critical threshold range logic, common options and generated usage, multiple levels of verbosity, debug mode etc), dramatically reducing the time to write high quality plugins down to mere hours and at the same time vastly improving the quality of the final code through code reuse, as well as benefitting from generic future improvements to the underlying libraries.
This gives each plugin the misleading appearance of being very short, because only the some of the very core logic of what you're trying to achieve is displayed in the plugin itself, mostly composition of utility functions, and the error handling is often handled in custom libraries too, so it may appear that a simple one line field extraction or 'curl()' or 'open_file()' utility function call has no error handling at all around it but under the hood the error handling is handled inside the function inside a library, same for HBase Thrift API connection, Redis API connection etc so the client code as seen in the top level plugins knows it succeeded or otherwise the framework would have errored out with a specific error message such as "connection refused" etc... there is a lot of buried error checking code and a lot of utility functions so many operations become one-liners at the top level instead of huge programs that are hard to read and maintain.
I've tried to keep the quality here high so a lot of plugins I've written over the years haven't made it in to this collection, there are a lot still pending import, a couple others
check_syslog-ng_stats.pl are in the
more/ directory until I get round to reintegrating and testing them with my current framework to modernize them, although they should still work with the tiny utils.pm from the standard nagios plugins collection.
I'm aware of Nagios::Plugin but my libraries have a lot more utility functions and I've written them to be highly convenient to develop with.
Some older plugins may not adhere to all of the criteria above so most have been filed away under the
older/ directory (they were used by people out there in production so I didn't want to remove them entirely). Older plugins also indicate that I haven't run or made updates to them in a few years so they're in basic maintenance mode and may require minor tweaks or updates.
If you're new remember to check out the
older/ directory for more plugins that are less current but that you might find useful such as RAID checks for Linux MD Raid, 3ware / LSI MegaRaid / Dell Perc Raid Controllers (which are actually rebranded LSI MegaRaid so you can use the same check - I also recommend the widely used Dell OpenManage Check).
Feedback, Feature Requests, Improvements and Patches are welcome.
Patches are accepted in the form of Github pull requests, for which you will receive attribution automatically as Github tracks these merges.
Support for Updates / Bugs Fixes / Feature Requests
Since there are a lot of programs covering a lot of different technologies in this project, so remember to look at the software versions each program was written / tested against (documented in --help for each program, also found near the top of the source code in each program). Newer versions of software seem to change a lot these days especially in the Big Data & NoSQL space so plugins may require updates for newer versions.
Please make sure you have run
make update first to pull the latest updates including library sub-modules and build the latest CPAN / PyPI module dependencies, (see Quick Setup above).
Make sure you run the code by hand on the command line with
-v -v -v for additional debug output and paste the full output in to the issue ticket. If you want to anonymize your hostnames/IP addresses etc you may use the
scrub.pl tool found in my DevOps Perl Tools repo.
Detailed Build Instructions
git clone https://github.com/harisekhon/nagios-plugins cd nagios-plugins make build
Some plugins like
check_yum.py can be copied around independently but most newer more sophisticated plugins require the co-located libraries I've written so you should
git clone && make on each machine you deploy this code to or just use the pre-built Docker image which has all plugins and dependencies inside.
You may need to install the GNU make system package if the
make command isn't found (
yum install make /
apt-get install make)
To build just the Perl or Python dependencies for the project you can do
make perl or
If you only want to use one plugin, you can do
make perl-libs or
make python-libs and then just install the potential one or two dependencies specific to that one plugin if it has any, which is much quicker than building the whole project.
make builds will install yum rpms / apt debs dependencies automatically as well as a load of Perl CPAN & Python PyPI libraries. To pick and choose what to install follow the Manual Build section instead
This has become quite a large project and will take at least 10 minutes to build. The build is automated and tested on RHEL / CentOS 5/6/7 & Debian / Ubuntu systems.
Make sure /usr/local/bin is in your
$PATH when running make as otherwise it'll fail to find
Python VirtualEnv / Perlbrew localized installs
The automated build will use 'sudo' to install required Perl CPAN & Python PyPI libraries to the system unless running as root or it detects being inside Perlbrew or VirtualEnv. If you want to install some of the common Perl / Python libraries such as Net::DNS and LWP::* using your OS packages instead of installing from CPAN / PyPI then follow the Manual Build section instead.
Download the Nagios Plugins, Lib and Pylib git repos as zip files:
Unzip all and move Lib and Pylib to the
pylib folders under nagios plugins.
unzip nagios-plugins-master.zip unzip pylib-master.zip unzip lib-master.zip mv -v nagios-plugins-master nagios-plugins mv -v pylib-master pylib mv -v lib-master lib mv -vf pylib nagios-plugins/ mv -vf lib nagios-plugins/
Proceed to install CPAN and PyPI modules for whichever programs you want to use using your usual procedure - usually an internal mirror or proxy server to CPAN and PyPI, or rpms / debs (some libraries are packaged by Linux distributions).
All CPAN modules are listed in
All PyPI modules are listed in
sudo pip install --index https://host.domain.com/api/pypi/repo/simple --trusted host.domain.com -r requirements.txt
sudo pip install --proxy hari:mypassword@proxy-host:8080 -r requirements.txt
Mac OS X
The automated build also works on Mac OS X but you will need to download and install Apple XCode development libraries. I also recommend you get HomeBrew to install other useful tools and libraries you may need like OpenSSL, Snappy and MySQL for their development headers and tools such as wget (these packages are automatically installed if Homebrew is installed on Mac OS X):
brew install openssl snappy mysql wget
Perl CPAN Crypt::SSLeay
To avoid the following cpan install error:
fatal error: 'openssl/opensslv.h' file not found #include
specify the path to the OpenSSL lib installed by HomeBrew:
sudo OPENSSL_INCLUDE=/usr/local/opt/openssl/include OPENSSL_LIB=/usr/local/opt/openssl/lib cpan Crypt::SSLeay
Perl CPAN DBD::mysql
DBI cpan module is installed as well as the
openssl HomeBrew package.
You may need to add the OpenSSL library path explicitly in
mysql_config to avoid the following error:
Checking if libs are available for compiling... Can't link/include C library 'ssl', 'crypto', aborting.
Once you're sure that OpenSSL is installed via HomeBrew (done as part of the automated build), find
mysql_config and edit the line
You may get errors trying to install to Python library paths even as root on newer versions of Mac, sometimes this is caused by pip 10 vs pip 9 and downgrading will work around it:
sudo pip install --upgrade pip==9.0.1 make sudo pip install --upgrade pip make
If you want to use any of the ZooKeeper content znode based checks (eg. for HBase / SolrCloud etc) based on check_zookeeper_znode.pl or any of the checksolrcloud*_zookeeper.pl programs you will also need to install the zookeeper libraries which has a separate build target due to having to install C bindings as well as the library itself on the local system. This will explicitly fetch the tested ZooKeeper 3.4.8, you'd have to update the
ZOOKEEPER_VERSION variable in the Makefile if you want a different version.
This downloads, builds and installs the ZooKeeper C bindings which Net::ZooKeeper needs. To clean up the working directory afterwards run:
Fetch my library repos which are included as submodules (they're shared between this and other repos containing various programs I've written over the years).
git clone https://github.com/harisekhon/nagios-plugins cd nagios-plugins git submodule init git submodule update
Then install the Perl CPAN and Python PyPI modules as listed in the next sections.
For Mac OS X see the Mac OS X section from Automated Build instructions.
Perl CPAN Modules
If installing the Perl CPAN or Python PyPI modules via your package manager or by hand instead of via the Automated Build From Source section, then read the requirements.txt and setup/cpan-requirements.txt files for the lists of Python PyPI and Perl CPAN modules respectively that you need to install.
You can install the full list of CPAN modules using this command:
sudo cpan $(sed 's/#.*//' < setup/cpan-requirements.txt)
and install the full list of PyPI modules using this command:
sudo pip install -r requirements.txt
Net::ZooKeeper (for various ZooKeeper content checks for Kafka, HBase, SolrCloud etc)
check_zookeeper_znode.pl check_zookeeper_child_znodes.pl check_hbase_*_znode.pl check_solrcloud_*_zookeeper.pl
The above listed programs require the Net::ZooKeeper Perl CPAN module but this is not a simple
cpan Net::ZooKeeper, that will fail. Follow these instructions precisely or debug at your own peril:
# install C client library export ZOOKEEPER_VERSION=3.4.8 [ -f zookeeper-$ZOOKEEPER_VERSION.tar.gz ] || wget -O zookeeper-$ZOOKEEPER_VERSION.tar.gz http://www.mirrorservice.org/sites/ftp.apache.org/zookeeper/zookeeper-$ZOOKEEPER_VERSION/zookeeper-$ZOOKEEPER_VERSION.tar.gz tar zxvf zookeeper-$ZOOKEEPER_VERSION.tar.gz cd zookeeper-$ZOOKEEPER_VERSION/src/c ./configure make sudo make install # now install Perl module using C library with the correct linking cd ../contrib/zkperl perl Makefile.PL --zookeeper-include=/usr/local/include/zookeeper --zookeeper-lib=/usr/local/lib LD_RUN_PATH=/usr/local/lib make sudo make install
After this check it's properly installed by doing
perl -e "use Net::ZooKeeper"
which should return no errors if successful.
Some plugins, especially ones under the older/ directory such as those that check 3ware/LSI raid controllers, SVN, VNC etc require external binaries to work, but the plugins will tell you if they are missing. Please see the respective vendor websites for 3ware, LSI etc to fetch those binaries and then re-run those plugins.
check_puppet.rb plugin uses Puppet's native Ruby libraries to parse the Puppet config and as such will only be run where Puppet is properly installed.
check_logserver.py "Syslog to MySQL" plugin will need the Python MySQL module to be installed which you should be able to find via your package manager. If using RHEL/CentOS do:
sudo yum install MySQL-python
or try install via pip, but this requires MySQL to be installed locally in order to build the Python egg...
sudo easy_install pip sudo pip install MySQL-python
make update. This will git pull and then git submodule update which is necessary to pick up corresponding library updates.
If you update often and want to just quickly git pull + submodule update but skip rebuilding all those dependencies each time then run
make update-no-recompile (will miss new library dependencies - do full
make update if you encounter issues).
There are full multi-level suites of tests against this repository and its libraries.
Continuous Integration is run on this repo with tests for success and failure scenarios:
- Unit Tests - 1200+ unit tests covering the Perl library and Python library
- Integration tests checking dependency integration, usage
- Custom tests for various languages and build systems, linting, coding style, and other standardizations
- Functional Tests - 800+ full functional tests/ using dozens of Docker Images for full API testing of the various technologies
To trigger all tests run:
which will start with the underlying libraries, then move on to top level integration tests and finally functional tests using docker containers if docker is available.
Bugs & Workarounds
Kafka dependency NetAddr/IP/InetBase autoload bug
If you encounter the following error when trying to use
Can't locate auto/NetAddr/IP/InetBase/AF_INET6.al in @INC
This is an upstream bug related to autoloader, which you can work around by editing
NetAddr/IP/InetBase.pm and adding the following line explicitly near the top just after
On Linux this is often at
/usr/local/lib64/perl5/NetAddr/IP/InetBase.pm and on Mac
You can find the location using
perl_find_library_path.pl NetAddr::IP::InetBase or
perl_find_library_path.sh NetAddr::IP::InetBase from the DevOps Perl Tools and DevOps Bash Tools repos.
You may also need to install Socket6 from CPAN.
This fix is now fully automated in the Make build by patching the
NetAddr/IP/InetBase.pm file and always including Socket6 in dependencies (UPDATE: this fix is broken on recent versions of Mac due to the addition of System Integrity Protection which doesn't allow editing the system files even with sudo to root - a workaround would be to install the libraries to a local PERLBREW and fix there).
Alternatively you can try the Python version
check_kakfa.py which works in similar fashion.
MongoDB dependency Readonly library bug
The MongoDB Perl driver from CPAN doesn't seem to compile properly on RHEL5 based systems. PyMongo rewrite was considered but the extensive library of functions results in better code quality for the Perl plugins, it's easier to just upgrade your OS to RHEL6.
The MongoDB Perl driver does compile on RHEL6 but there is a small bug in the Readonly CPAN module that the MongoDB CPAN module uses. When it tries to call Readonly::XS, a MAGIC_COOKIE mismatch results in the following error:
Readonly::XS is not a standalone module. You should not use it directly. at /usr/local/lib64/perl5/Readonly/XS.pm line 34.
The workaround is to edit the Readonly module and comment out the
eval 'use Readonly::XS' on line 33 of the Readonly module.
This is located here on Linux:
and here on Max OS X:
IO::Socket::SSL doesn't respect ignoring self-signed certs in recent version(s) eg. 2.020
Recent version(s) of IO::Socket::SSL (2.020) seem to fail to respect options to ignore self-signed certs. The workaround is to create the hidden touch file below in the same top-level directory as the library to make this it include and use Net::SSL instead of IO::Socket::SSL.
Python SSL certificate verification problems
If you end up with an error like:
[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:765)
It can be caused by an issue with the underlying Python + libraries due to changes in OpenSSL and certificates. One quick fix is to do the following:
sudo pip uninstall -y certifi && sudo pip install certifi==2015.04.28
Kafka Scala Nagios Plugin - Scala version of the Python and Perl Kafka plugins found here, build provides a self-contained jar with Kerberos support.
DevOps Python Tools - 80+ DevOps CLI tools for AWS, Hadoop, HBase, Spark, Log Anonymizer, Ambari Blueprints, AWS CloudFormation, Linux, Docker, Spark Data Converters & Validators (Avro / Parquet / JSON / CSV / INI / XML / YAML), Elasticsearch, Solr, Travis CI, Pig, IPython
DevOps Bash Tools - 200+ DevOps Bash scripts, advanced
.toprc, Utility Code Library used by CI and all my GitHub repos - includes code for AWS, Kubernetes, Kafka, Docker, Git, Code & build linting, package management for Linux / Mac / Perl / Python / Ruby / Golang, and lots more random goodies
DevOps Perl Tools - 25+ DevOps CLI tools for Hadoop, HDFS, Hive, Solr/SolrCloud CLI, Log Anonymizer, Nginx stats & HTTP(S) URL watchers for load balanced web farms, Dockerfiles & SQL ReCaser (MySQL, PostgreSQL, AWS Redshift, Snowflake, Apache Drill, Hive, Impala, Cassandra CQL, Microsoft SQL Server, Oracle, Couchbase N1QL, Dockerfiles, Pig Latin, Neo4j, InfluxDB), Ambari FreeIPA Kerberos, Datameer, Linux...
HAProxy-configs - 80+ HAProxy Configs for Hadoop, Big Data, NoSQL, Docker, Elasticsearch, SolrCloud, HBase, Cloudera, Hortonworks, MapR, MySQL, PostgreSQL, Apache Drill, Hive, Presto, Impala, ZooKeeper, OpenTSDB, InfluxDB, Prometheus, Kibana, Graphite, SSH, RabbitMQ, Redis, Riak, Rancher etc.
Dockerfiles - 50+ DockerHub public images for Docker & Kubernetes - Hadoop, Kafka, ZooKeeper, HBase, Cassandra, Solr, SolrCloud, Presto, Apache Drill, Nifi, Spark, Mesos, Consul, Riak, OpenTSDB, Jython, Advanced Nagios Plugins & DevOps Tools repos on Alpine, CentOS, Debian, Fedora, Ubuntu, Superset, H2O, Serf, Alluxio / Tachyon, FakeS3
anonymize.py- anonymizes configs / logs for posting online - replaces hostnames/domains/FQDNs, IPs, passwords/keys in Cisco/Juniper configs, custom extensible phrases like your name or your company name
validate_json/yaml/ini/xml/avro/parquet.py- validates JSON, YAML, INI (Java Properties), XML, Avro, Parquet including directory trees, standard input and even optionally 'single quoted json' and multi-record bulk JSON data formats as found in MongoDB and Hadoop / Big Data systems.
PySpark Avro / CSV / JSON / Parquet data converters
code reCaser for SQL / Pig / Neo4j / Hive HQL / Cassandra / MySQL / PostgreSQL / Impala / MSSQL / Oracle / Dockerfiles
Hive / Pig => Elasticsearch / SolrCloud indexers
Hadoop HDFS performance debugger, native checksum extractor, HDFS file retention & snapshot retention policy scripts, HDFS file stats, XML & running Hadoop cluster config differ
watch_url.pl- debugs load balanced web farms via multiple queries to a URL - returns HTTP status codes, % success across all requests, timestamps, round trip times, and optionally the output
tools for Ambari, Pig, Hive, Spark + IPython Notebook, Solr CLI
Ambari Blueprints tool & templates
AWS CloudFormation templates
DockerHub API tools including more search results and fetching repo tags (not available in official Docker tooling)
My Perl library - used throughout this code as a submodule to make the programs in this repo short
My Python library - Python version of the above library, also heavily leveraged to keep programs in this repo short
Enterprise Monitoring Systems
Compatible Monitoring Solutions
The biggest advantage of Nagios-compatible monitoring systems is the multitude of Nagios Plugins created by domain experts in each field to monitor almost everything out there.
Nagios Plugins are widely and freely available across the internet, especially at the original Nagios Exchange and the newer Icinga Exchange (at which you'll see this project at the top of the most viewed list).
The following enterprise monitoring systems are compatible with Nagios Plugins and this project:
Nagios Core - the original widely used open source monitoring system that set the standard
- Nagios Command Configuration
- Nagios Service Configuration
- NRPE - Nagios Remote Plugin Executor - most plugins check network services like NoSQL datastores but you can use NRPE for plugins that check the local system eg.
- PNP4Nagios - widely used metrics auto graphing add-on for Nagios
Nagios IX - commercial version of the open source Nagios Core with more features and enterprise support. Most people using Nagios use the free version since most of the benefit is in the plugins themselves.
Icinga2 - popular open source Nagios fork rewritten with more features, Icinga retains the all important Nagios Plugin compatibility, but also has native distributed monitoring, rule based configuration, a REST API and native metrics graphing integrations via Graphite, InfluxDB and OpenTSDB to create graphs from the plugins' perfdata
Shinken - open source modular Nagios reimplementation in Python, Nagios config compatible, with distributed monitoring architecture, high availability, host / service discovery, forwards plugins' metrics perfdata via the Graphite protocol to Graphite or InfluxDB, see documentation
OpenNMS - open source enterprise-grade network management platform with native graphing, geo-mapping, Grafana integration, as well as Elasticsearch event forwarder integration for Kibana search/visualization. OpenNMS can execute Nagios Plugins via NRPE, see NRPEMonitor documentation
Sensu - open-core distributed monitoring system, compatible with both Nagios and Zabbix plugins. Enterprise Edition contains metrics graphing integrations for Graphite, InfluxDB or OpenTSDB to graph the plugins' metrics perfdata
Check_MK - open-core Nagios-based monitoring solution with rule-based configuration, service discovery and agent-based multi-checks integrating MRPE - MK's Remote Plugin Executor. See
adapter_check_mk.pywhich can run any Nagios Plugin and convert its output to Check_MK local check format. Has built-in metrics graphing via PNP4Nagios, Enterprise Edition can send metrics to Graphite and InfluxDB via the Graphite protocol, see documentation
Geneos - proprietary non-standard monitoring, was used by a couple of banks I worked for. Geneos does not follow Nagios standards so integration is provided via
adapter_geneos.pywhich if preprended to any standard nagios plugin command will execute and translate the results to the CSV format that Geneos expects, so Geneos can utilize any Nagios Plugin using this program
Microsoft SCOM - Microsoft Systems Center Operations Manager, can run Nagios Plugins as arbitrary Unix shell scripts with health / warning / error expression checks, see the Microsoft technet documentation
Incompatible Monitoring Solutions
Zabbix - open source monitoring solution with in-built graphing, distributed monitoring and auto discovery but unfortunately not Nagios Plugin compatible, some integration can be done via a wrapper script (we tried exactly this in 2012 but didn't like it enough to switch from Nagios), see this community forum thread for more information and code
Metrics Graphing Integrations
Graphite, InfluxDB, Prometheus, OpenTSDB, PNP4Nagios
Many monitoring systems will already auto-graph the performance metric data from these nagios plugins via PNP4Nagios but you can also forward it to newer more specialised metrics monitoring and graphing systems such as Graphite, InfluxDB, OpenTSDB and Prometheus (this last one is the most awkward as it requires pull rather than passively receiving).
The above list of enterprise monitoring systems documents each one's integration capabilities with links to their documentation.
Metrics Collection Integrations
You can also execute these Nagios Plugins outside of any nagios-compatible monitoring server and forward just the metrics to the major metrics monitoring systems using the following tools:
- Collectd - metrics collection daemon - can execute Nagios Plugins to collect their perfdata via the exec plugin. Can send metrics to Graphite, InfluxDB (via Graphite protocol), Prometheus (via exporter for scrape target) and OpenTSDB. See also the collectd nagios plugin which allows Nagios to query collectd metrics to apply alerts against them
- Telegraf - metrics collection daemon - can execute Nagios Plugins via
data_format="nagios"and pass the Nagios Plugin perfdata to InfluxDB, Graphite, Prometheus and OpenTSDB - see the InfluxDB data input formats documentation
Other Metrics Integration Add-Ons
- PNP4Nagios - widely used open source auto-graphing add-on for Nagios open source and similar Nagios-based monitoring systems, see list of enterprise monitoring systems above to see which ones bundle this
- Graphios - sends perfdata collected by Nagios to metrics graphing systems like Graphite or InfluxDB (via Graphite protocol)
Antiquated Monitoring Solutions You Probably Shouldn't Still Be Using Today
You may also be interested in the feature matrix on the Wikipedia page - Comparison of network monitoring systems.
More 3rd Party Nagios Plugins
This is a list of the best and most interesting 3rd party plugins, several of which I have used or come across over the years that deserve mention, usually due to their better quality than the typical Nagios Exchange / Monitoring Exchange plugins.
- check_openmanage - Dell PowerEdge servers hardware monitoring plugin using Dell OpenManage. Written by Trond Hasle Amundsen - checks RAID, Processors, Memory, Fans, Temperature, Power Supplies etc. Top quality widely used plugin - one of my all time favourites
- Consol Labs checks - one of the very best quality publishers of Nagios Plugins (I have a lot of respect for this team):
- WebInject - authenticate through HTTP Login portals and check the inside. Widely used and flexible via external XML config. Excellent - I used to use this a lot and it's probably the best of it's kind
- Jolokia - JMX-HTTP bridge to make monitoring JMX easier via Rest calls from non-JVM scripting languages. This is far more scalable than running lots of JVM Nagios Plugins which have higher startup overhead
- check_jmx4perl - use with Jolokia
- Percona plugins - MySQL plugins from MySQL specialists
- check_drbd - can't remember if this is the DRBD plugin I used to use, but iirc it was good at tracking lag on secondary and catch-up
- check_tsd - OpenTSDB metrics query
- check_prometheus_metric.sh - I don't normally rate bash scripts as Nagios Plugins but this is in the official project so it's worth a look
- collectd-nagios - queries Collectd metrics for Nagios alerting
- collectd exec-nagios.px - executes a Nagios Plugin and returns the metrics to Collectd to forward on to one of the many compatible metrics graphing solutions
- Datameer references this project in the Datameer docs from version 3 onwards. Datameer wrote 1 example nagios plugin on that page, then referenced the 9 additional plugins here in the links section at the bottom along with the official Nagios links