[ZBXNEXT-4001] Introduce unique keys for Items and Triggers Created: 2017 Jul 28 Updated: 2021 May 24 Resolved: 2021 May 24 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Templates (T) |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Change Request | Priority: | Major |
Reporter: | Vitaly Zhuravlev | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 7 |
Labels: | export, import, item, template, templates, trigger, xml | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
Description |
Hi
Problem is this: 1. As far as I know. item key identifier during XML import is key_ - but it has parameters that you might wanna tune inside square brackets [], like some sort of timeout. Once you do it on your test server and then try to import it: Zabbix thinks it's brand new item. And creates new item instead of linking to the previous one. If you tick 'delete missing items' - then you would loose all item's history, which is not acceptable for many users. 2. Same applies for triggers. During import trigger expression+ trigger name is identifier. So if you decided to rename your trigger (there was a typo there for example, or decided to improve the description) or fine tune your trigger's expression. Then you would either get duplicated triggers during XML import or loose all your trigger events (if you tick 'delete missing triggers'). Introducing unique static ID(key) for triggers and items could solve that templates distribution and update problem. |
Comments |
Comment by Glebs Ivanovskis (Inactive) [ 2017 Jul 28 ] |
|
Comment by Vitaly Zhuravlev [ 2017 Jul 28 ] |
1,2 doesn't work in reality. There always be errors or new enhancements in your templates no matter what. Just like in any software. Also remember that templates are written by users too. |
Comment by Vitaly Zhuravlev [ 2017 Aug 08 ] |
It's suggested to use GUID generated when creating new item/item proto or trigger/trigger proto for the first time via frontend. |
Comment by Vitaly Zhuravlev [ 2017 Aug 18 ] |
Updating template triggers via XML also breaks IT services since old trigger is deleted and no longer mapped to the Service. |
Comment by Valeriy Zabawski [ 2017 Aug 18 ] |
@vzhuravlev |
Comment by Vitaly Zhuravlev [ 2017 Aug 18 ] |
Valeriy, It's only an idea how this could be fixed in future releases. There is no such workaround i'm afraid right now. |
Comment by Valeriy Zabawski [ 2017 Aug 18 ] |
Okay. Thank you anyway. |
Comment by Alexei Vladishev [ 2021 May 24 ] |
This functionality has been implemented in Zabbix 5.4. |