1) Discovery + actions do not allow for specifying rules to determine some host addition options. i.e., it's not possible to set a discovery rule forcing the host to use DNS name not IP address, nor to fully specify host|dns|ip settings. Problematic in the attempt to use Discovery in place of the incomplete XML import, or unreasonable GUI for adding large numbers of hosts.
2) I've found that Configuration->Actions->EventSource
iscovery menu, it's not possible to enable/disable an action by either clicking the current status in the "Status" column, OR by selecting the check-box and clicking the "Enable selected" or "Disable selected" buttons. Only by editing the action rule, selecting a change of state from the drop-down menu, and saving will the change in state be made. No errors are generated in this, just looks to be a code dead-end.
3) I've got a large number (several thousand) Linux boxen that use a read-only root filesystem. I'm currently not able to use the Discovery method to add them effectively since by default system.hostname is used (which translates to the FQDN), breaking my site-standard for using only hostname for the 'host' key... IMO the 'dns' column in the hosts table is for storing this, no? This would be a useful option to propagate, since it exists both in the XML import and GUI creation interfaces.
If we had an option in the zabbix_agentd.conf file allowing for something like:
That would make it much more flexible for differing user implementations.
Currently I'm finding all of the import functions have varying degrees of support for host|template addition, and none of them (but the GUI) seems to have FULL support.
Just trying to give some feedback from my attempt to use all available options (which there are indeed a few
in evaluating Zabbix.
Cheers,
/eli
2) I've found that Configuration->Actions->EventSource
iscovery menu, it's not possible to enable/disable an action by either clicking the current status in the "Status" column, OR by selecting the check-box and clicking the "Enable selected" or "Disable selected" buttons. Only by editing the action rule, selecting a change of state from the drop-down menu, and saving will the change in state be made. No errors are generated in this, just looks to be a code dead-end.3) I've got a large number (several thousand) Linux boxen that use a read-only root filesystem. I'm currently not able to use the Discovery method to add them effectively since by default system.hostname is used (which translates to the FQDN), breaking my site-standard for using only hostname for the 'host' key... IMO the 'dns' column in the hosts table is for storing this, no? This would be a useful option to propagate, since it exists both in the XML import and GUI creation interfaces.
If we had an option in the zabbix_agentd.conf file allowing for something like:
Hostname=`/bin/hostname -s`
#or
Hostname_type = [ fqdn | short ]
#or
Hostname_type = [ fqdn | short ]
That would make it much more flexible for differing user implementations.
Currently I'm finding all of the import functions have varying degrees of support for host|template addition, and none of them (but the GUI) seems to have FULL support.
Just trying to give some feedback from my attempt to use all available options (which there are indeed a few
in evaluating Zabbix.Cheers,
/eli