Posted on July 3rd, 2010 by admin
Both in our own corporate network and at our customer’s sites we use the open source tool Nagios for system monitoring. It’s suitable from small installations to very large server landscapes. With our biggest installation we monitor the health of more than 1900 servers for our customer. Useful tools and plugins evolved from our daily work with Nagios. Some of them we want to share and offer them as open source.
15 Responses to “Nagios Plugins & AddOns”
October 20th, 2009 at 18:50
I would like use your check_oracle plugin for nagios.
November 16th, 2010 at 16:30
I really appreciate your contribution to open source community. check_logfiles is my fav and now I just started looking at thruk still reviewing. I am manager around 1200+ servers across 2 datacenters out of 25000 Services 6000 are logparsing services using check_logfiles so you are making my day every time I get requirements on logparsing. What I am looking is a kind of rss feed where I can subscribe to know what’s new plugin (or) version updates added to Nagios Plugins & AddOns Inventory on your website. Please let me know the link if u have such to which I can subscribe. Once again thanks and appreciate your contribution to Open Community.
November 16th, 2010 at 21:09
@lausser & @roland – Thanks for the links, All the best for future success of Console Labs Inventions.
November 16th, 2010 at 21:11
I am using Safari and I have a nice link called Subscribe in Mail :-) which is nice to have all the update in one place which is Apple Mail.
Günter Bretterebner Says:
March 8th, 2012 at 14:32
Wäre es grundsätzlich möglich, Nagios in der QShell direkt auf der i5 laufen zu lassen?
Wir haben einige PC-Server als nws auf der i5 integriert, da wäre es naheliegend, das Monitoring “ganz unten” anzusiedeln.
Mit freundlichen Grüßen
May 9th, 2012 at 5:49
Hello: I would like use a plugin for swift. Have you ? Thanks
Fernando Xavier Says:
May 24th, 2012 at 17:01
Hi, are the links from check_mssql_help download pages broken?
May 29th, 2012 at 11:36
i am going to use your check_oracle plugin to monitor the sessions to oracle DB. i think your plugin can do it.
operating System: Solaris database oracle
what i want to do i will list below ;
sqlplus / as sysdba
SQL> select current_utilization, max_utilization, limit_value from v$resource_limit where resource_name =’sessions’;
CURRENT_UTILIZATION MAX_UTILIZATION LIMIT_VALUE ——————- ————— ————————- ————— 386 404 1528
if the current utilization reaches 1500 alert critical, 1450 warning state. else normal.
can you tell me how i can use your plugin to do the following. i have nagios installed on a different machine to monitor systems.
June 3rd, 2012 at 12:17
i have compiled your plugin n i am running the following on bash
./check_oracle_health -connect=nagios/test@//192.168.7.52:1521/test; -mode tnsping
i am getting errors….
nashrah@VBOX:/usr/local/nagios/libexec$ ./check_oracle_health -connect=nagios/test@//192.168.7.52:1521/test; -mode tnsping Please select a mode Copyright (c) 2008 Gerhard Lausser
Check various parameters of Oracle databases
Usage: check_oracle_health [-v] [-t ] –connect= –username= –password= –mode= –tablespace= check_oracle_health [-h | --help] check_oracle_health [-V | --version]
Options: –connect the connect string –username the oracle user –password the oracle user’s password –warning the warning range –critical the critical range –mode the mode of the plugin. select one of the following keywords: tnsping (Check the reachability of the server) connection-time (Time to connect to the server) connected-users (Number of currently connected users) session-usage (Percentage of sessions used) process-usage (Percentage of processes used) rman-backup-problems (Number of rman backup errors during the last 3 days) sga-data-buffer-hit-ratio (Data Buffer Cache Hit Ratio) sga-library-cache-gethit-ratio (Library Cache (Get) Hit Ratio) sga-library-cache-pinhit-ratio (Library Cache (Pin) Hit Ratio) sga-library-cache-reloads (Library Cache Reload (and Invalidation) Rate) sga-dictionary-cache-hit-ratio (Dictionary Cache Hit Ratio) sga-latches-hit-ratio (Latches Hit Ratio) sga-shared-pool-reload-ratio (Shared Pool Reloads vs. Pins) sga-shared-pool-free (Shared Pool Free Memory) pga-in-memory-sort-ratio (PGA in-memory sort ratio) invalid-objects (Number of invalid objects in database) stale-statistics (Find objects with stale optimizer statistics) corrupted-blocks (Number of corrupted blocks in database) tablespace-usage (Used space in tablespaces) tablespace-free (Free space in tablespaces) tablespace-remaining-time (Remaining time until a tablespace is full) tablespace-fragmentation (Free space fragmentation index) tablespace-io-balance (balanced io of all datafiles) tablespace-can-allocate-next (Segments (of a tablespace) can allocate next extent) datafile-io-traffic (io operations/per sec of a datafile) datafiles-existing (Percentage of the maximum possible number of datafiles) soft-parse-ratio (Percentage of soft parses) switch-interval (Time between redo log file switches) retry-ratio (Redo buffer allocation retries) redo-io-traffic (Redo log io bytes per second) roll-header-contention (Rollback segment header contention) roll-block-contention (Rollback segment block contention) roll-hit-ratio (Rollback segment hit ratio (gets/waits)) roll-wraps (Rollback segment wraps (per sec)) roll-extends (Rollback segment extends (per sec)) roll-avgactivesize (Rollback segment average active size) seg-top10-logical-reads (user objects among top 10 logical reads) seg-top10-physical-reads (user objects among top 10 physical reads) seg-top10-buffer-busy-waits (user objects among top 10 buffer busy waits) seg-top10-row-lock-waits (user objects among top 10 row lock waits) event-waits (processes wait events) event-waiting (time spent by processes waiting for an event) enqueue-contention (percentage of enqueue requests which must wait) enqueue-waiting (percentage of time spent waiting for the enqueue) latch-contention (percentage of latch get requests which must wait) latch-waiting (percentage of time a latch spends sleeping) sysstat (change of sysstat values over time) flash-recovery-area-usage (Used space in flash recovery area) flash-recovery-area-free (Free space in flash recovery area) sql (any sql command returning a single number) list-tablespaces (convenience function which lists all tablespaces) list-datafiles (convenience function which lists all datafiles) list-enqueues (convenience function which lists all enqueues) list-latches (convenience function which lists all latches) list-events (convenience function which lists all events) list-background-events (convenience function which lists all background events) list-sysstats (convenience function which lists all statistics from v$sysstat)
--name the name of the tablespace, datafile, wait event, latch, enqueue, or sql statement depending on the mode. --name2 if name is a sql statement, this statement would appear in the output and the performance data. This can be ugly, so name2 can be used to appear instead. --regexp if this parameter is used, name will be interpreted as a regular expression. --units one of %, KB, MB, GB. This is used for a better output of mode=sql and for specifying thresholds for mode=tablespace-free --ident outputs instance and database names --commit turns on autocommit for the dbd::oracle module
Tablespace-related modes check all tablespaces in one run by default. If only a single tablespace should be checked, use the –name parameter. The same applies to datafile-related modes.
tablespace-remaining-time will take historical data into account. The number of days in the past can be given with the –lookback parameter. (Default: 30)
In mode sql you can url-encode the statement so you will not have to mess around with special characters in your Nagios service definitions. Instead of –name=”select count(*) from v$session where status = ‘ACTIVE’” you can say –name=select%20count%28%2A%29%20from%20v%24session%20where%20status%20%3D%20%27ACTIVE%27 For your convenience you can call check_oracle_health with the –encode option and it will encode the standard input.
Send email to email@example.com if you have questions regarding use of this software. Please include version information with all correspondence (when possible, use output from the –version option of the plugin itself). -mode: command not found