Details
-
New Feature
-
Resolution: Done
-
Minor
-
None
-
Professional Edition
Description
Why is there a predefined list for the probes? What if this would check the folder where the probes are in for the dropdown so that you can add custom probes like check_mtr to the list? Is there any reason for that?
Attachments
Activity
Probes have some configuration definitions to describe default options to the UI:
$probe = 'check_snmp_cisco_wlc';
$config['probes'][$probe]['enable'] = 1;
$config['probes'][$probe]['descr'] = 'Check operability of Cisco APs on a controller.';
$config['probes'][$probe]['args']['default'] = "-H %hostname% -v %snmp_version% --snmpport=%snmp_port% -t %snmp_timeout%";
$config['probes'][$probe]['args']['v2c'] = "-C %snmp_community%";
$config['probes'][$probe]['args']['v1'] = $config['probes'][$probe]['args']['v2c'];
$config['probes'][$probe]['args']['v3_authpriv'] = "-u %snmp_authname% -A %snmp_authalgo% -a %snmp_authpass% -P %snmp_cryptoalgo% -p %snmp_cryptopass%";
$config['probes'][$probe]['args']['v3_authnopriv'] = "-u %snmp_authname% -A %snmp_authalgo% -a %snmp_authpass%";
$config['probes'][$probe]['args']['v3_noauthnopriv'] = "-u %snmp_authname%";
We don't show everything in the directory in part to prevent situations where people just add random plugins without configuring any options and generating lots of queries about why they don't work, and in part because the original design of the probes system was somewhat different.
To make use of a probe we don't yet have a definition for, you just write one and put it in config.php (and/or send it to us to get incorporated into the probe definitions properly).
We generally try to promote expansion of the defaults rather than single use case customisation.
Thank you that was exactly what I needed and it is working as expected. I understand why you do not want to maintain every monitoring plugin that exist.