Nice catch!

But I don't like the idea of placing executable script somewhere in zabbix configs directory. First, <something>.d usually means that everything inside is included in resulting config, second, the script may be used without zabbix too.

I suggest not to change userparameters, but to add this line for basic and advanced templates in zabbix_integration_examples/README.md:

• copy ssl_cert_check.sh file into /usr/local/bin on host

I was running into an issue where if the script was in /usr/local/bin I received an Unsupported Key Item error in Zabbix when it tried to run discovery. The resolution for me was the same as found in #47 to move the file to the .d location. Not sure if there is a better spot for it to still function as expected.

Weird. Either /usr/local/bin was not in PATH or zabbix user did not have access to that path or to the script(wrong permissions), or something like AppArmor/SELinux did not allow that.

Then let's write it like that:

• copy ssl_cert_check.sh file into /usr/local/bin on host (note: make sure that zabbix user can execute the script)