[ZBX-11754] Quotation marks absent in triggerns section when exporting Template with Web Scenario Created: 2017 Jan 28  Updated: 2018 May 09  Resolved: 2018 May 09

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Documentation (D)
Affects Version/s: 3.2.3, 3.4.9rc3
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Denis Assignee: Unassigned
Resolution: Won't fix Votes: 0
Labels: export, xml
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 16.04.1 LTS
zabbix_server (Zabbix) 3.2.3
Revision 64610 21 December 2016, compilation time: Dec 21 2016 14:09:47

Issue Links:
Duplicate
is duplicated by ZBX-13650 Import of template containing web sce... Closed
is duplicated by ZBX-11911 Importing XML template through API fa... Closed
is duplicated by ZBX-12405 Failed to import Web template with we... Closed

 Description   

To reproduce:
1) Create web scenario with some tests in it.
2) Export it and try to import it.

Expected results:

  • import will succeed

Actual results:
Import will fail with error message:
Incorrect item key "web.test.fail[mysite.com]" provided for trigger expression on "Zabbix server".

Explanation:
Error happens due to missing single quotation mark ' in the .xml

Actual:
<expression>{Zabbix server:web.test.fail[mysite.com].min(5m)}<>0</expression>

Correct:
<expression>{Zabbix server:web.test.fail['mysite.com'].min(5m)}<>0</expression>

 Comments   
Comment by Miks Kronkalns [ 2017 Apr 07 ]

Can't reproduce it. Tested in 3.2.3 as well as in trunk.

The proper syntax should be without quotes. Denis, please make sure that your Zabbix has latest patches installed and let us know if you still can repeat it.

Comment by Jon Beilke [ 2017 May 03 ]

Was this importing via frontend or API?

If it's API I've run into a similar issue in ZBX-11911 (with or w/o quotation marks)

Comment by Alexander Vladishev [ 2018 May 09 ]

This issue still reproducible in 3.4.9rc3.

Comment by Alexander Vladishev [ 2018 May 09 ]

This problem already mentioned in our documentation. This is caused by bugs in PHP 7.0. Upgrading to PHP 7.1 should solve this problem.

Generated at Wed Apr 24 12:18:06 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.