[ZBX-16550] Web scenario's don't start monitoring Created: 2019 Aug 23  Updated: 2024 Apr 10  Resolved: 2019 Sep 05

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: API (A)
Affects Version/s: 4.4.0alpha1, 4.4.0alpha2
Fix Version/s: 4.4.0alpha3, 4.4 (plan)

Type: Problem report Priority: Major
Reporter: Milenco Mulder Assignee: Mārtiņš Tālbergs (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Team: Team B
Team: Team B
Sprint: Sprint 56 (Sep 2019), Sprint 55 (Aug 2019)
Story Points: 0.5

 Description   

Steps to reproduce:

  1. Use Zabbix server 4.4.0alpha1 or alpha2 (zabbix_server (Zabbix) 4.4.0alpha2 Revision 36f514195c 19 August 2019, compilation time: Aug 15 2019 10:07:23)
    1. Debian 10 server
    2. Use repo deb http://repo.zabbix.com/zabbix/4.3/debian buster main
  2. Create a new web-scenario under a host.

Result:
The newly create web-scenario does not start to monitor. An older web-scenario created under Zabbix 3.x is still working but newly creates ones don't start monitoring. The "Web monitoring" widget in the Dashboard shows status 'Unknown'  for these broken web-scenario's.

The zabbix_server.log doesn't show any relevant information.

 Comments   
Comment by Alexander Vladishev [ 2019 Aug 23 ]

Problem in API, because when creating web scenario items, API does not create the corresponding entries in the item_rtdata table.

Comment by Mārtiņš Tālbergs (Inactive) [ 2019 Aug 27 ]

IMPLEMENTED in development branch feature/ZBX-16550-4.3

Comment by Mārtiņš Tālbergs (Inactive) [ 2019 Sep 03 ]

Fixed in:

Comment by Mārtiņš Tālbergs (Inactive) [ 2019 Sep 03 ]

If you have also encountered this issue, just an upgrade to 4.4.0beta1 would not fix this issue for web scenarios that are already created. In order to fix such web scenarios, you should just recreate them - this can be easily achieved by cloning them (the cloned version will have real-time-data items).

Generated at Fri Apr 19 23:29:20 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.