[ZBX-8357] Low Level Discovery Fails when Existing Items Keys Exist on Host Created: 2014 Jun 14 Updated: 2017 May 30 Resolved: 2014 Jun 16 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 2.2.3 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Major |
| Reporter: | Robert V. Bolton | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | duplicates, lld | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
If I apply a template to a host which contains items to monitor network interfaces such as eth0 and eth1 and then add a discovery rule to the template to discover additional network interfaces, the discovery rule will fail with an error that item keys can not created because keys already exist for eth0 and eth1. Should the low-level discovery fail when duplicate items are discovered or should it skip these duplicate items? |
| Comments |
| Comment by Aleksandrs Saveljevs [ 2014 Jun 16 ] |
|
Suppose a host already has manually created items "net.if.in[eth0]" and "net.if.in[eth1]". Suppose also that LLD discovers eth0, eth1 and eth2. Then LLD will create "net.if.in[eth2]", but will mention in the error message that it could not create items for eth0 and eth1. So this works as designed. |
| Comment by richlv [ 2014 Jun 16 ] |
|
a frequently requested usecase is migrating from non-lld setup to lld setup. you already have items and you do not want to lose data. currently there does not seem to be a way to do that without manual messing with the db ...requested at ZBXNEXT-1484, will link this issue as a duplicate |