[1.3.5] autodiscovery
Hi,
a problem with autodiscovery.
I know not all things are implemented, but to get a first impression
what will be available in 1.4 I did some checks, anyway.
I configured a rule for our test environment and three servers
were found.
The actions configured were:
1. Send mail to user Zabbix - works.
Problem: {HOSTNAME} = *UNKNOWN* in the mail.
I did not check, whether using {IPADDRESS} will work, but I guess so.
2. Add host to group "Newly discovered servers" - works.
Problem: one host is added based on IP-address while the same host is
already in the DB, but without IP-Address. Now I have 4 hosts in this
hostgroup !
I think the last one was due to the missing IP-Address for the host in the DB.
I'll remove the host from the discovered group, add the IP-Address to the
already discovered host and try again.
The actions based on discovery rules are not shown in the Monitoring / Actions form.
OK, as said above, autodiscovery seems to work partially.
That's what I expected and behaves according to the release notes.
However, installing a new agent does simply nothing now.
No addition to the hostgroup, no message sent, ...
Will that be added or do we have to run autodiscovery for all networks ?
This needs a lot of load on the server. Since enabling it, the load average
is above 3 (avg for the last 5 checks) for one single network.
Regards,
Norbert.
a problem with autodiscovery.
I know not all things are implemented, but to get a first impression
what will be available in 1.4 I did some checks, anyway.
I configured a rule for our test environment and three servers
were found.
The actions configured were:
1. Send mail to user Zabbix - works.
Problem: {HOSTNAME} = *UNKNOWN* in the mail.
I did not check, whether using {IPADDRESS} will work, but I guess so.
2. Add host to group "Newly discovered servers" - works.
Problem: one host is added based on IP-address while the same host is
already in the DB, but without IP-Address. Now I have 4 hosts in this
hostgroup !
I think the last one was due to the missing IP-Address for the host in the DB.
I'll remove the host from the discovered group, add the IP-Address to the
already discovered host and try again.
The actions based on discovery rules are not shown in the Monitoring / Actions form.
OK, as said above, autodiscovery seems to work partially.
That's what I expected and behaves according to the release notes.
However, installing a new agent does simply nothing now.
No addition to the hostgroup, no message sent, ...
Will that be added or do we have to run autodiscovery for all networks ?
This needs a lot of load on the server. Since enabling it, the load average
is above 3 (avg for the last 5 checks) for one single network.
Regards,
Norbert.