Hello.
It would be great if it was possible to use "DNS name" macro in the name of a trigger.
For example trigger name "Virtual host {HOSTNAME} has low disk space" could be written more specificly to "Virtual host {HOSTNAME} at {DNSNAME} has low disk space". According to the documentation there's currently only {IPADDRESS} available from the basic host information.
We've got about hundred hardware nodes, which are holding over thousand virtual hosts (virtualized servers). The virtual hosts are named according to their numerical ID number. The hardware nodes have zabbix agents running and periodically executed custom script, which collects and sends data about the virtual hosts through zabbix_sender. Now, if one of the virtual hosts runs out of disk space, the alert message is not very useful because it contains only the vague ID number of the virtual host. Domain name would be extremely useful there.
Overall Zabbix has been very easy to customize to meet our requirements.
Thanks, and cheers.
It would be great if it was possible to use "DNS name" macro in the name of a trigger.
For example trigger name "Virtual host {HOSTNAME} has low disk space" could be written more specificly to "Virtual host {HOSTNAME} at {DNSNAME} has low disk space". According to the documentation there's currently only {IPADDRESS} available from the basic host information.
We've got about hundred hardware nodes, which are holding over thousand virtual hosts (virtualized servers). The virtual hosts are named according to their numerical ID number. The hardware nodes have zabbix agents running and periodically executed custom script, which collects and sends data about the virtual hosts through zabbix_sender. Now, if one of the virtual hosts runs out of disk space, the alert message is not very useful because it contains only the vague ID number of the virtual host. Domain name would be extremely useful there.
Overall Zabbix has been very easy to customize to meet our requirements.
Thanks, and cheers.
Comment