[ZBX-16524] Aggregated checks not able to locate item keys in Host groups where the keys actually exist Created: 2019 Aug 15  Updated: 2024 Apr 10  Resolved: 2019 Aug 23

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 4.4.0alpha2
Fix Version/s: 4.4.0alpha2, 4.4 (plan)

Type: Problem report Priority: Major
Reporter: Sergejs Olonkins Assignee: Vladislavs Sokurenko
Resolution: Fixed Votes: 0
Labels: aggregateditems
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: XML File Aggregated_checks_issue.xml     File zabbix_server_2019-08-16.log    
Issue Links:
Causes
caused by ZBXNEXT-5040 Separate configuration and realtime f... Closed
Team: Team A
Sprint: Sprint 55 (Aug 2019)
Story Points: 0.125

 Description   

Problem description: in current master release (4.4.0alpha2) Aggregated items become unsupported with error "No items for key '.....' in group(s) '......' " even though items with such keys actually exist for hosts under the corresponding host group. Exactly the same setup works perfectly fine in Zabbix 4.2.6rc1.

Steps to reproduce:

  1. Create host group "Hostgroup 1" with several hosts.
  2. Create a zabbix agent type item with key "agent.ping" (type of information = numeric (unsigned)) for each host.
  3. Create another Host group "Aggregate data" with a signle host.
  4. Create an item with type = "Zabbix aggregate", key = grpavg["Hostgroup 1","agent.ping",last], and type of information = Numeric (float).
  5. Wait for the items to collect some data.

Result: the status of the "Zabbix aggregate" item is Not supported" with the following error returned in the pop-up: 'No items for key "agent.ping" in group(s) "Hostgroup 1".'

Expected: the Zabbix aggregate item should collect and process data from all items with key "agent.ping" located on all hosts under "Hostgroup 1".

Exported configuration: Aggregated_checks_issue.xml



 Comments   
Comment by Vladislavs Sokurenko [ 2019 Aug 19 ]

Fixed in:

  • pre-4.4.0alpha2 (trunk) a1380e04e76
Generated at Wed Apr 24 07:49:43 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.