Monitoring other hosts than localhost

[bilbolodz]

Added parameter {$HOSTNAME} to specify monitored host (other than localhost)

[scoopex]

Thanks for the merge request.

Two things:

• As i can remember mod_status just returns the statistics for the entire apache server instance. Therefore putting it just in the default vhost seemed to be a good solution because this can be seperated by other vhosts in the installation. What is your usage scenario to monitor other hosts like localhost?
• I currently maintain the template on zabbix 3.4, can you submit a 3.4 template for consistency reasons? (4.0 format just added a few additional sections which need to be purged from your pull request)

[bilbolodz]

For some reasons (config of apache is beyond my role) your script is not working with "127.0.0.1" but IS working with localhost:

/usr/local/lib/zabbix/externalscripts/zabbix_check_apache-mod-status total 85 127.0.0.1 FAIL: Unable to get scoreboard FAIL /usr/local/lib/zabbix/externalscripts/zabbix_check_apache-mod-status total 85 localhost Scoreboard: _W_._W____._.................................................................................................................................................................................................................................................... 256

That's why I need to put hostname into parameters. Of course it could be "fixed" in script code, but I think it's not a good idea.

According 3.4 vs 4.0 zabbix template versions unfortunately I'm working on Zabbix 4.0.

[scoopex]

Sorry, i would like to take this, but you change changes also the template, which creates problems with existing installations. Applying the change to a existing installation create a second set of apache items. Therefore you might search for a solution with lower impact or by shareing the zabbix /server-status on 127.0.0.1.