Rev 87 | Details | Compare with Previous | Last modification | View Log | RSS feed
| Rev | Author | Line No. | Line |
|---|---|---|---|
| 2 | daniel-mar | 1 | |
| 2 | TODO |
||
| 3 | ---- |
||
| 4 | |||
| 5 | - allow changing automatic help page to describe which individual ranges stand for (is it already possible, by getting the argument object and then changing its help text?) |
||
| 6 | - everywhere getter and setter instead of accessing class member variables |
||
| 7 | - ipfm monitor: dygraph has MIT license |
||
| 8 | - *.conf files: /daten sollte nicht in den example conf's stehen. irgendwie anders machen (Aber achtung: wir symlinken die config files in unserem /etc ) |
||
| 9 | - idea: a script that converts the output of an EXISTING nagios plugin into VNag Weboutput. So an arbitary Nagios script can be forwarded to other systems over HTTP |
||
| 10 | - make all plugins "web enabled" |
||
| 87 | daniel-mar | 11 | - In the framework create an easy function, which generates a simple default HTML header and footer |
| 2 | daniel-mar | 12 | - should error details, e.g. defective hard disks at the mdstat monitor be Verbosity=Summary, or Verbosity=AdditionalInformation ? |
| 13 | - idea for a new plugin: sudo /daten/scripts/tools/check_etc_perms | grep -v "world readable" | grep -v "world executable" |
||
| 14 | - should putputID, passwordOut and privateKey be a default argument? Then you can use encryption/signing for all plugins by default |
||
| 15 | - In re syntax checking/getopt: |
||
| 16 | * Evaluate if PHP 7.1 (with getopt()'s $optind) is able to detect unexpected CLI parameters for us (so we can output a syntax warning) |
||
| 17 | * Limit warning range numbers (avoid user adds too many, e.g. "-w A,B,C" although only 2 are allowed) |
||
| 18 | |||
| 19 | Future |
||
| 20 | ------ |
||
| 21 | |||
| 22 | - For arguments (warning/critical), also accept mixed UOMs, e.g. MB and % |
||
| 23 | - In re usage page: |
||
| 24 | * Automatic creation of usage page. Which arguments are necessary? |
||
| 25 | * Automatically generate syntax? |
||
| 26 | - Allow individual design via CSS |
||
| 27 | - Check if regex of validateLongOpt() is accurate |
||
| 28 | |||
| 29 | Unsure |
||
| 30 | ------ |
||
| 31 | |||
| 32 | - Automatically encrypt/sign via a global config setting? |