| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 10_check_snmp_storage_error_handling | [PATCH] check_snmp_storage: fix SNMP error handling, see #33 | Louis Sautier <sautier.louis@gmail.com> | no | 2018-01-29 | ||
| 11_check_snmp_int_agent_workaround | [PATCH] Workaround for buggy SNMP agents not removing deleted interfaces. If exact match is requested, only use the interface with the highest index. Some buggy SNMP agents forget to delete interfaces which are gone (like ppp or tunnel interfaces). |
Jochen Friedrich <j.friedrich@nwe.de> | no | 2018-03-14 | ||
| 12_check_snmp_mem_perf | [PATCH] Better support for buffered/cached memory in Linux Exclude buffered memory from perfdata output, if `-b` option is specified |
jimbobmcgee <jimbobmcgee@users.noreply.github.com> | no | 2018-03-20 | ||
| 51_fix_privacy_doc | ## 51_fix_privacy_doc by Jan Wagner ## ## DP: Fixing potential privacy breach by fetching data from sourceforge.net commit 084af86fe6ee55135144ac44f661ff139434fdc3 Fix potential privacy breach of HTML documentation |
Jan Wagner <waja@cyconet.org> | no | 2014-03-02 | ||
| 13_check_snmp_process_new_features | [PATCH] Minor feature updates to check_snmp_process.pl The following features are included: 1. Added new `-T` option, to report/check against the total RAM of all matched processes, rather than the highest value 2. Warn/Crit values are now optional for `-m` and `-u` options, allowing for capture of these in perfdata without requiring thresholds 3. Perfdata is now always written if `-F` is supplied, even if there were no matched process (i.e. `num_process=0 memory_usage=0 cpu_usage=0`). |
jimbobmcgee <jimbobmcgee@users.noreply.github.com> | no | 2018-03-20 | ||
| 14_check_snmp_int_ign | [PATCH] added ign-admindown, ign-emptyalias options. fixed unitialized variable warning | Stanislav Datskevych <me@nek0.net> | no | 2019-01-09 | ||
| 15_check_snmp_int_spaces | [PATCH] Add spaces only if necessary, resolving bug #32 | PGranado <pgranado@pt.lu> | no | 2019-03-22 | ||
| 16_check_snmp_win_max_message_size | [PATCH] Add -o option (max message size) in check_snmp_win | =?UTF-8?q?Mathias=20V=C3=A9drines?= <mvedrines@capensis.fr> | no | 2020-02-21 | ||
| 17_check_snmp_storage_okifempty | [PATCH] check_snmp_storage.pl: add support for allowing considering OK if no storage found matching given criteria | roa <roa@eurotux.com> | no | 2020-03-09 | ||
| 18_check_snmp_int_fix_perf_out | [PATCH] fix perf_out not defined error | =?UTF-8?q?Pawe=C5=82=20Szafer?= <pszafer@gmail.com> | no | 2020-03-16 | ||
| 19_check_snmp_int_remove_unneeded_my | [PATCH] Update check_snmp_int.pl Removed unneeded my |
Steffen Schoch <dein@gehirn-mag.net> | no | 2021-04-27 | ||
| 20_check_snmp_int_avaid_huge_amount_of_regex | [PATCH] Update check_snmp_int.pl Effectively reverting commit 9f9b15a926d8795935b54626dc3ab9e5becb2763 and doing it in a different way that avoids adding huge amounts of regex, that may not run on older systems. Removed the added " =~ s/\./_/r ", instead replacing the dots (.) in the regex that was meant for it in the first place -> line 967. |
kwork-er <88452982+kwork-er@users.noreply.github.com> | no | 2021-08-05 | ||
| 21_check_snmp_load_update_fortiswitch_and_fortigate4.3 | [PATCH] check_snmp_load.pl: Add Fortiswitch & 4.3+ firmware fortigate This commit adds support for checking the fortiswitch CPU usage and also fortigate 4.3 and above firmware. This OID got changed but to keep backwards compatibility and not to break already running platforms depending on this the new OID was added as new type. |
Martin Botka <16738302+Haxk20@users.noreply.github.com> | no | 2022-08-01 | ||
| 22_check_snmp_storage_fix_space_btrfs | [PATCH] No out of space check_snmp_storage warning on btrfs We've noticed out of space condition in one of btrfs filesystems monitored with check_snmp_storage; problem was not detected by check_snmp_storage. Filesystem status: root@mysrv:~# btrfs fi df -b /mnt Data, single: total=2222194688, used=2222194688 System, DUP: total=8388608, used=16384 System, single: total=4194304, used=0 Metadata, DUP: total=484835328, used=163921920 Metadata, single: total=8388608, used=0 GlobalReserve, single: total=16777216, used=0 root@mysrv:~# df -B1 /mnt Filesystem 1B-blocks Used Available Use% Mounted on /dev/mapper/myvg 3221225472 2566848512 0 100% /mnt Net-snmp snmp infos for this fs: hrStorageTable (used by check_snmp_storage): iso.3.6.1.2.1.25.2.3.1.1.69 = INTEGER: 69 // hrStorageIndex iso.3.6.1.2.1.25.2.3.1.2.69 = OID: iso.3.6.1.2.1.25.2.1.4 // hrStorageType iso.3.6.1.2.1.25.2.3.1.3.69 = STRING: "/mnt" // hrStorageDescr iso.3.6.1.2.1.25.2.3.1.4.69 = INTEGER: 4096 // hrStorageAllocationUnits iso.3.6.1.2.1.25.2.3.1.5.69 = INTEGER: 786432 // hrStorageSize iso.3.6.1.2.1.25.2.3.1.6.69 = INTEGER: 626672 // hrStorageUsed dskTable (not used by check_snmp_storage): iso.3.6.1.4.1.2021.9.1.1.19 = INTEGER: 19 // dskIndex iso.3.6.1.4.1.2021.9.1.2.19 = STRING: "/mnt" // dskPath iso.3.6.1.4.1.2021.9.1.3.19 = STRING: "/dev/mapper/myvg" // dskDevice iso.3.6.1.4.1.2021.9.1.4.19 = INTEGER: -1 // dskMinimum iso.3.6.1.4.1.2021.9.1.5.19 = INTEGER: 10 // dskMinPercent iso.3.6.1.4.1.2021.9.1.6.19 = INTEGER: 3145728 // dskTotal (Total size of the disk/partion (kBytes)) iso.3.6.1.4.1.2021.9.1.7.19 = INTEGER: 0 // dskAvail (Available space on the disk) iso.3.6.1.4.1.2021.9.1.8.19 = INTEGER: 2506688 // dskUsed (Used space on the disk) iso.3.6.1.4.1.2021.9.1.9.19 = INTEGER: 80 // dskPercent (Percentage of space used on disk) iso.3.6.1.4.1.2021.9.1.10.19 = INTEGER: 0 // dskPercentNode (Percentage of inodes used on disk) iso.3.6.1.4.1.2021.9.1.11.19 = Gauge32: 3145728 // dskTotalLow Total size of the disk/partion (kBytes). Together with dskTotalHigh composes 64-bit number) iso.3.6.1.4.1.2021.9.1.12.19 = Gauge32: 0 // dskTotalHigh (Total size of the disk/partion (kBytes). Together with dskTotalLow composes 64-bit number.) iso.3.6.1.4.1.2021.9.1.13.19 = Gauge32: 0 // dskAvailLow (Available space on the disk (kBytes). Together with dskAvailHigh composes 64-bit number.) iso.3.6.1.4.1.2021.9.1.14.19 = Gauge32: 0 // dskAvailHigh (Available space on the disk (kBytes). Together with dskAvailLow composes 64-bit number.) iso.3.6.1.4.1.2021.9.1.15.19 = Gauge32: 2506688 // dskUsedLow (Used space on the disk (kBytes). Together with dskUsedHigh composes 64-bit number.) iso.3.6.1.4.1.2021.9.1.16.19 = Gauge32: 0 // dskUsedHigh (Used space on the disk (kBytes). Together with dskUsedLow composes 64-bit number.) iso.3.6.1.4.1.2021.9.1.100.19 = INTEGER: 1 // dskErrorFlag (Error flag signaling that the disk or partition is under the minimum required space configured for it.) iso.3.6.1.4.1.2021.9.1.101.19 = STRING: "/mnt: less than 10% free (= 0%)" // dskErrorMsg (A text description providing a warning and the space left on the disk.) The cause of problem is that in btrfs free space may be less than total-used and by default check_snmp_storage checks used space which was in this case about 80% (with 0% available in the same time and OS was throwing OOS errors on write). The solution is to configure warn/crit levels for %free not %used and use avail from dskTable because hrStorageTable does not provide this info (check_snmp_storage calculates free=total-used which is wrong for btrfs as above). This patch works ok for us (this allows one to use new -u switch to use dskTable and its avail info instead of default hrStorageTable and its free=total-used calculation). This also adds a few spaces to plugin output for better message readability. |
IB Development Team <dev@ib.pl> | no | 2023-01-19 | ||
| 50_disable_epn | ## 50_disable_epn by Jan Wagner <waja@cyconet.org> ## ## DP: leave marks to disable epn |
no |