docs: regenerate READMEs and Director baskets after lib v3.0.0 HELP_TEXTS

Rerun `tools/update-readmes` and `tools/check2basket --auto` to pick up
cascaded changes from earlier commits in this series:

- lib v3.0.0 added a central `--test` HELP_TEXTS entry, so all plugins
  that accept `--test` now show the same standardized help line. The
  regenerated READMEs reflect the new help output.
- cpu-usage and disk-io DESCRIPTIONs had typographic minus signs and
  curly apostrophes replaced with plain ASCII (RUF001 fix in the
  ruff cleanup commit). The regenerated Director baskets pick up
  the sanitized text.
- sap-open-concur-com's `--service` parameter gained a fixed
  allowed-values list, so its Director basket now exposes a
  Datalist-typed field plus a new service-name list instead of a
  free-form string.

No plugin code change in this commit; all diffs are auto-generated
artifacts catching up with previously committed code.

Author: markuslf

check-plugins/apache-httpd-version/README.md

@@ -36,7 +36,7 @@ Checks the installed Apache httpd version against the endoflife.date API and ale
 usage: apache-httpd-version [-h] [-V] [--always-ok] [--check-major]
                             [--check-minor] [--check-patch] [--insecure]
                             [--no-proxy] [--offset-eol OFFSET_EOL]
-                            [--timeout TIMEOUT]
+                            [--test TEST] [--timeout TIMEOUT]
 
 Checks the installed Apache httpd version against the endoflife.date API and
 alerts if the version is end-of-life or if newer major, minor, or patch
@@ -63,6 +63,8 @@ options:
   --offset-eol OFFSET_EOL
                         Alert n days before ("-30") or after an EOL date ("30"
                         or "+30"). Default: -30 days
+  --test TEST           For unit tests. Needs "path-to-stdout-file,path-to-
+                        stderr-file,expected-retc".
   --timeout TIMEOUT     Network timeout in seconds. Default: 8 (seconds)
 ```
 

check-plugins/apache-solr-version/README.md

@@ -35,7 +35,7 @@ Checks the installed Apache Solr version against the endoflife.date API and aler
 usage: apache-solr-version [-h] [-V] [--always-ok] [--check-major]
                            [--check-minor] [--check-patch] [--insecure]
                            [--no-proxy] [--offset-eol OFFSET_EOL]
-                           [--path PATH] [--timeout TIMEOUT]
+                           [--path PATH] [--test TEST] [--timeout TIMEOUT]
 
 Checks the installed Apache Solr version against the endoflife.date API and
 alerts if the version is end-of-life or if newer major, minor, or patch
@@ -64,6 +64,8 @@ options:
                         or "+30"). Default: -30 days
   --path PATH           Local path to your Apache Solr binary. Default:
                         /opt/solr/bin/solr
+  --test TEST           For unit tests. Needs "path-to-stdout-file,path-to-
+                        stderr-file,expected-retc".
   --timeout TIMEOUT     Network timeout in seconds. Default: 8 (seconds)
 ```
 

check-plugins/composer-version/README.md

@@ -36,7 +36,7 @@ Checks the installed Composer version against the endoflife.date API and alerts
 usage: composer-version [-h] [-V] [--always-ok] [--check-major]
                         [--check-minor] [--check-patch] [--insecure]
                         [--no-proxy] [--offset-eol OFFSET_EOL] [--path PATH]
-                        [--timeout TIMEOUT]
+                        [--test TEST] [--timeout TIMEOUT]
 
 Checks the installed Composer version against the endoflife.date API and
 alerts if the version is end-of-life or if newer major, minor, or patch
@@ -65,6 +65,8 @@ options:
                         or "+30"). Default: -30 days
   --path PATH           Local path to your composer binary. Default:
                         /usr/bin/composer
+  --test TEST           For unit tests. Needs "path-to-stdout-file,path-to-
+                        stderr-file,expected-retc".
   --timeout TIMEOUT     Network timeout in seconds. Default: 8 (seconds)
 ```
 

check-plugins/cpu-usage/icingaweb2-module-director/cpu-usage.json

@@ -146,7 +146,7 @@
                 "tpl-service-generic"
             ],
             "max_check_attempts": 5,
-            "notes": "Reports CPU utilization percentages for all available time categories (user, system, idle, nice, iowait, irq, softirq, steal, guest, guest_nice) plus the overall cpu-usage (100 \u2212 idle \u2212 nice). Thresholds (WARN/CRIT) are checked against user, system, iowait, and cpu-usage. An alert is raised only if the threshold is exceeded for COUNT consecutive runs, suppressing short spikes and focusing on sustained load. Perfdata is emitted for every field to enable full graphing. Extended stats (context switches, interrupts, etc.) are included if supported on this platform. This check is cross-platform and works on Linux, Windows, and all psutil-supported systems. The check stores its short trend state locally in an SQLite DB to evaluate sustained load across runs.",
+            "notes": "Reports CPU utilization percentages for all available time categories (user, system, idle, nice, iowait, irq, softirq, steal, guest, guest_nice) plus the overall cpu-usage (100 - idle - nice). Thresholds (WARN/CRIT) are checked against user, system, iowait, and cpu-usage. An alert is raised only if the threshold is exceeded for COUNT consecutive runs, suppressing short spikes and focusing on sustained load. Perfdata is emitted for every field to enable full graphing. Extended stats (context switches, interrupts, etc.) are included if supported on this platform. This check is cross-platform and works on Linux, Windows, and all psutil-supported systems. The check stores its short trend state locally in an SQLite DB to evaluate sustained load across runs.",
             "notes_url": "https://linuxfabrik.github.io/monitoring-plugins/check-plugins/cpu-usage/",
             "object_name": "tpl-service-cpu-usage",
             "object_type": "template",
@@ -195,7 +195,7 @@
                 "tpl-service-generic"
             ],
             "max_check_attempts": 5,
-            "notes": "Reports CPU utilization percentages for all available time categories (user, system, idle, nice, iowait, irq, softirq, steal, guest, guest_nice) plus the overall cpu-usage (100 \u2212 idle \u2212 nice). Thresholds (WARN/CRIT) are checked against user, system, iowait, and cpu-usage. An alert is raised only if the threshold is exceeded for COUNT consecutive runs, suppressing short spikes and focusing on sustained load. Perfdata is emitted for every field to enable full graphing. Extended stats (context switches, interrupts, etc.) are included if supported on this platform. This check is cross-platform and works on Linux, Windows, and all psutil-supported systems. The check stores its short trend state locally in an SQLite DB to evaluate sustained load across runs.",
+            "notes": "Reports CPU utilization percentages for all available time categories (user, system, idle, nice, iowait, irq, softirq, steal, guest, guest_nice) plus the overall cpu-usage (100 - idle - nice). Thresholds (WARN/CRIT) are checked against user, system, iowait, and cpu-usage. An alert is raised only if the threshold is exceeded for COUNT consecutive runs, suppressing short spikes and focusing on sustained load. Perfdata is emitted for every field to enable full graphing. Extended stats (context switches, interrupts, etc.) are included if supported on this platform. This check is cross-platform and works on Linux, Windows, and all psutil-supported systems. The check stores its short trend state locally in an SQLite DB to evaluate sustained load across runs.",
             "notes_url": "https://linuxfabrik.github.io/monitoring-plugins/check-plugins/cpu-usage/",
             "object_name": "tpl-service-cpu-usage-windows",
             "object_type": "template",

check-plugins/deb-updates/README.md

@@ -45,7 +45,7 @@ bind9-dnsutils/stable,stable-security 1:9.18.33-1~deb12u2 amd64 [upgradable from
 
 ```text
 usage: deb-updates [-h] [-V] [--always-ok] [--only-critical] [--query QUERY]
-                   [--timeout TIMEOUT] [-w WARN]
+                   [--test TEST] [--timeout TIMEOUT] [-w WARN]
 
 Checks for available APT package updates on Debian, Ubuntu, and compatible
 systems. Reports the number of pending updates and upgrades, and alerts when
@@ -63,6 +63,8 @@ options:
                       updates is printed. Have a look at the README for a list
                       of available columns. Example: `--query='package like
                       "bind9-%"'`. Default: 1
+  --test TEST         For unit tests. Needs "path-to-stdout-file,path-to-
+                      stderr-file,expected-retc".
   --timeout TIMEOUT   Network timeout in seconds. Default: 60 (seconds)
   -w, --warning WARN  Minimum number of pending packages to trigger a WARNING.
                       Default: 1

check-plugins/disk-io/icingaweb2-module-director/disk-io.json

@@ -210,7 +210,7 @@
                 "tpl-service-generic"
             ],
             "max_check_attempts": 5,
-            "notes": "Checks disk I/O bandwidth over time and alerts on sustained saturation, not short spikes. The check records per-disk read/write counters and then derives current (R1/W1) and period averages (R{COUNT}/W{COUNT}). It compares the period\u2019s total bandwidth against the maximum ever observed for that disk (RWmax). WARN/CRIT trigger if the period average exceeds the configured percentage of RWmax for COUNT consecutive runs. On Linux, the check also monitors the system-wide iowait percentage (CPU time spent waiting for I/O). The raw iowait value is normalized by multiplying it with the number of logical CPUs, so that 100% always means one CPU core is fully I/O-saturated, regardless of the total number of CPUs. This makes the default thresholds (80/90%) work consistently across different hardware. Like bandwidth alerts, iowait alerts require COUNT consecutive threshold violations. Perfdata is emitted for each disk (busy_time, read_bytes, read_time, write_bytes, write_time) and for iowait, so you can graph trends. On Linux the check automatically focuses on \"real\" block devices with mountpoints; on Windows it uses psutil\u2019s disk counters. Optionally, `--top` lists the processes that generated the most I/O traffic (read/write totals) to help identify offenders. This check is cross-platform and works on Linux, Windows, and all psutil-supported systems. The check stores its short trend state locally in an SQLite DB to evaluate sustained load across runs.",
+            "notes": "Checks disk I/O bandwidth over time and alerts on sustained saturation, not short spikes. The check records per-disk read/write counters and then derives current (R1/W1) and period averages (R{COUNT}/W{COUNT}). It compares the period's total bandwidth against the maximum ever observed for that disk (RWmax). WARN/CRIT trigger if the period average exceeds the configured percentage of RWmax for COUNT consecutive runs. On Linux, the check also monitors the system-wide iowait percentage (CPU time spent waiting for I/O). The raw iowait value is normalized by multiplying it with the number of logical CPUs, so that 100% always means one CPU core is fully I/O-saturated, regardless of the total number of CPUs. This makes the default thresholds (80/90%) work consistently across different hardware. Like bandwidth alerts, iowait alerts require COUNT consecutive threshold violations. Perfdata is emitted for each disk (busy_time, read_bytes, read_time, write_bytes, write_time) and for iowait, so you can graph trends. On Linux the check automatically focuses on \"real\" block devices with mountpoints; on Windows it uses psutil's disk counters. Optionally, `--top` lists the processes that generated the most I/O traffic (read/write totals) to help identify offenders. This check is cross-platform and works on Linux, Windows, and all psutil-supported systems. The check stores its short trend state locally in an SQLite DB to evaluate sustained load across runs.",
             "notes_url": "https://linuxfabrik.github.io/monitoring-plugins/check-plugins/disk-io/",
             "object_name": "tpl-service-disk-io",
             "object_type": "template",
@@ -263,7 +263,7 @@
                 "tpl-service-generic"
             ],
             "max_check_attempts": 5,
-            "notes": "Checks disk I/O bandwidth over time and alerts on sustained saturation, not short spikes. The check records per-disk read/write counters and then derives current (R1/W1) and period averages (R{COUNT}/W{COUNT}). It compares the period\u2019s total bandwidth against the maximum ever observed for that disk (RWmax). WARN/CRIT trigger if the period average exceeds the configured percentage of RWmax for COUNT consecutive runs. On Linux, the check also monitors the system-wide iowait percentage (CPU time spent waiting for I/O). The raw iowait value is normalized by multiplying it with the number of logical CPUs, so that 100% always means one CPU core is fully I/O-saturated, regardless of the total number of CPUs. This makes the default thresholds (80/90%) work consistently across different hardware. Like bandwidth alerts, iowait alerts require COUNT consecutive threshold violations. Perfdata is emitted for each disk (busy_time, read_bytes, read_time, write_bytes, write_time) and for iowait, so you can graph trends. On Linux the check automatically focuses on \"real\" block devices with mountpoints; on Windows it uses psutil\u2019s disk counters. Optionally, `--top` lists the processes that generated the most I/O traffic (read/write totals) to help identify offenders. This check is cross-platform and works on Linux, Windows, and all psutil-supported systems. The check stores its short trend state locally in an SQLite DB to evaluate sustained load across runs.",
+            "notes": "Checks disk I/O bandwidth over time and alerts on sustained saturation, not short spikes. The check records per-disk read/write counters and then derives current (R1/W1) and period averages (R{COUNT}/W{COUNT}). It compares the period's total bandwidth against the maximum ever observed for that disk (RWmax). WARN/CRIT trigger if the period average exceeds the configured percentage of RWmax for COUNT consecutive runs. On Linux, the check also monitors the system-wide iowait percentage (CPU time spent waiting for I/O). The raw iowait value is normalized by multiplying it with the number of logical CPUs, so that 100% always means one CPU core is fully I/O-saturated, regardless of the total number of CPUs. This makes the default thresholds (80/90%) work consistently across different hardware. Like bandwidth alerts, iowait alerts require COUNT consecutive threshold violations. Perfdata is emitted for each disk (busy_time, read_bytes, read_time, write_bytes, write_time) and for iowait, so you can graph trends. On Linux the check automatically focuses on \"real\" block devices with mountpoints; on Windows it uses psutil's disk counters. Optionally, `--top` lists the processes that generated the most I/O traffic (read/write totals) to help identify offenders. This check is cross-platform and works on Linux, Windows, and all psutil-supported systems. The check stores its short trend state locally in an SQLite DB to evaluate sustained load across runs.",
             "notes_url": "https://linuxfabrik.github.io/monitoring-plugins/check-plugins/disk-io/",
             "object_name": "tpl-service-disk-io-windows",
             "object_type": "template",

check-plugins/disk-usage/README.md

@@ -41,7 +41,7 @@ usage: disk-usage [-h] [-V] [--always-ok] [-c CRIT]
                   [--exclude-regex EXCLUDE_REGEX] [--fstype FSTYPE]
                   [--include-pattern INCLUDE_PATTERN]
                   [--include-regex INCLUDE_REGEX] [--list-fstypes]
-                  [--perfdata-regex PERFDATA_REGEX] [-w WARN]
+                  [--perfdata-regex PERFDATA_REGEX] [--test TEST] [-w WARN]
 
 Checks used or free disk space for each mounted partition. By default, only
 physical devices are checked (hard disks, USB drives), ignoring pseudo and
@@ -94,6 +94,8 @@ options:
                         Only emit perfdata keys matching this Python regex.
                         For a list of perfdata keys, see the README or run
                         this plugin. Can be specified multiple times.
+  --test TEST           For unit tests. Needs "path-to-stdout-file,path-to-
+                        stderr-file,expected-retc".
   -w, --warning WARN    WARN threshold in the form `<number>[unit][method]`.
                         Unit is one of `%|K|M|G|T|P` (default: `%`). `K` means
                         kibibyte etc. Method is one of `USED|FREE` (default:

check-plugins/file-descriptors/README.md

@@ -29,7 +29,7 @@ Checks the system-wide file descriptor usage as a percentage of the kernel maxim
 
 ```text
 usage: file-descriptors [-h] [-V] [--always-ok] [-c CRIT] [--top TOP]
-                        [-w WARN]
+                        [--test TEST] [-w WARN]
 
 Checks the system-wide file descriptor usage as a percentage of the kernel
 maximum. Also lists the top processes consuming the most file descriptors to
@@ -44,6 +44,8 @@ options:
                        Default: 95
   --top TOP            Number of top processes to list by open file
                        descriptors. Default: 5
+  --test TEST          For unit tests. Needs "path-to-stdout-file,path-to-
+                       stderr-file,expected-retc".
   -w, --warning WARN   WARN threshold for file descriptor usage in percent.
                        Default: 90
 ```

check-plugins/grafana-version/README.md

@@ -34,7 +34,8 @@ Checks the installed Grafana version against the endoflife.date API and alerts i
 ```text
 usage: grafana-version [-h] [-V] [--always-ok] [--check-major] [--check-minor]
                        [--check-patch] [--insecure] [--no-proxy]
-                       [--offset-eol OFFSET_EOL] [--timeout TIMEOUT]
+                       [--offset-eol OFFSET_EOL] [--test TEST]
+                       [--timeout TIMEOUT]
 
 Checks the installed Grafana version against the endoflife.date API and alerts
 if the version is end-of-life or if newer major, minor, or patch releases are
@@ -61,6 +62,8 @@ options:
   --offset-eol OFFSET_EOL
                         Alert n days before ("-30") or after an EOL date ("30"
                         or "+30"). Default: -30 days
+  --test TEST           For unit tests. Needs "path-to-stdout-file,path-to-
+                        stderr-file,expected-retc".
   --timeout TIMEOUT     Network timeout in seconds. Default: 8 (seconds)
 ```
 

check-plugins/graylog-version/README.md

@@ -34,7 +34,8 @@ Checks the installed Graylog version against the endoflife.date API and alerts i
 ```text
 usage: graylog-version [-h] [-V] [--always-ok] [--check-major] [--check-minor]
                        [--check-patch] [--insecure] [--no-proxy]
-                       [--offset-eol OFFSET_EOL] [--timeout TIMEOUT]
+                       [--offset-eol OFFSET_EOL] [--test TEST]
+                       [--timeout TIMEOUT]
 
 Checks the installed Graylog version against the endoflife.date API and alerts
 if the version is end-of-life or if newer major, minor, or patch releases are
@@ -61,6 +62,8 @@ options:
   --offset-eol OFFSET_EOL
                         Alert n days before ("-30") or after an EOL date ("30"
                         or "+30"). Default: -30 days
+  --test TEST           For unit tests. Needs "path-to-stdout-file,path-to-
+                        stderr-file,expected-retc".
   --timeout TIMEOUT     Network timeout in seconds. Default: 8 (seconds)
 ```