[ZBXNEXT-1495] Network Discovery Unique Identifier Created: 2012 Oct 31 Updated: 2012 Nov 22 |
|
| Status: | Open |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Server (S) |
| Affects Version/s: | 2.0.3 |
| Fix Version/s: | None |
| Type: | Change Request | Priority: | Major |
| Reporter: | Marcus Oliveira | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 2 |
| Labels: | networkdiscovery, uniqueness | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOS 6.3 and Percona MySQL Server |
||
| Description |
|
Hi guys, It would be very nice the possibility to choose HOSTNAME as UNIQUE IDENTIFIER as the majority of servers have many IPs. The action fired based on on the discovery rule get confused when a server have more than one IP on reachable networks. Marcus |
| Comments |
| Comment by richlv [ 2012 Oct 31 ] |
|
are you discovering zabbix agent there ? |
| Comment by Marcus Oliveira [ 2012 Oct 31 ] |
|
The fastest response ever... thanks. If you are asking if the discovered serveres have Zabbix agent installed, the answer is "not always". Marcus |
| Comment by richlv [ 2012 Oct 31 ] |
|
so server should do reverse lookup and use the result as the uniqueness criteria ? |
| Comment by Marcus Oliveira [ 2012 Oct 31 ] |
|
That's a possibility. It was the first thing I thought. Marcus |
| Comment by Oleksii Zagorskyi [ 2012 Nov 22 ] |
|
See also |