[ZBX-18354] Zabbix discovery rule trying to create already created items Created: 2020 Sep 09 Updated: 2020 Sep 18 Resolved: 2020 Sep 18 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Server (S) |
Affects Version/s: | 4.0.23 |
Fix Version/s: | None |
Type: | Problem report | Priority: | Trivial |
Reporter: | Titas T | Assignee: | Aigars Kadikis |
Resolution: | Commercial support required | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Zabbix 4.0.22. |
Attachments: |
![]() ![]() ![]() ![]() |
Description |
Steps to reproduce:
Result: Cannot create item: item with the same key "tier3.jobs.mssql.dbmenabled[MSSQLSERVER]" already exists. see screenshot 549 |
Comments |
Comment by Aigars Kadikis [ 2020 Sep 18 ] |
Hello, thank you for contacting us. I see you are using only one variable to distinguish all discovery keys: This is a very sensitive thing to do. Please add some additional {#SECOND.MACRO} to item prototype definition in it will work much better. This is not really a bug. It's by design. If you have a lot of similar entities discovered you have to use more fields to make every entry unique. I will close this incident for now as it is not really a bug but a configuration issue. Kind regards, Aigars |
Comment by Titas T [ 2020 Sep 18 ] |
Thank you Aigars! |