[ZBX-16035] Multi-level Zapcat item keys not working with Zabbix 4.2 Created: 2019 Apr 23  Updated: 2019 Apr 23  Resolved: 2019 Apr 23

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F), Proxy (P), Server (S)
Affects Version/s: 4.2.0
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Chris Kistner Assignee: Zabbix Support Team
Resolution: Won't fix Votes: 0
Labels: zapcat
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File cannot-add-item.png     PNG File unsupported-item.png    

 Description   

In Zabbix 4.2.0 our Zapcat style items are now unsupported. I am not sure if this issue is related to ZBX-13783, since that issue looked like it would fix something like this.

Steps to reproduce:

  1. Start to create a new Item under a Host or Template
  2. Specify a multi-level (multiple square brackets) Key. eg 
    jmx[com.example.app:type=MyWebAp][ErrorResponseCount]
  1. Click on Add

Result:
When trying to Add a new Item, we get the current error in the 4.2.0 Frontend: 

We also get the "Invalid key" error message when trying to disable or change the state of the unsupported item.

I believe Zabbix 3.4 still allowed these kind of multi-level (zapcat) keys, and now that we're running Zabbix 4.2.0, the server changed the items to "Not Supported" - see the following issue when hovering over the unsupported item:

 Comments   
Comment by richlv [ 2019 Apr 23 ]

Correct, support for those was dropped in 4.0 - see https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400#disallowed_item_key_parameter_syntax .

Comment by Chris Kistner [ 2019 Apr 23 ]

Thank you @richlv.

We'll then just have to modify Zapcat, which we have already done in the past.

Please feel free to close this bug then.

Generated at Sat Apr 20 16:14:52 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.