[ZBX-22580] Nodata triggers after proxy becomes available Created: 2023 Mar 23  Updated: 2025 Feb 25  Resolved: 2025 Feb 07

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P)
Affects Version/s: 6.0.14, 6.0.26, 6.4.0, 6.4.11, 7.0.0beta1
Fix Version/s: 6.0.39rc1, 7.0.10rc1, 7.2.4rc1, 7.4.0alpha1

Type: Problem report Priority: Major
Reporter: Elina Kuzyutkina (Inactive) Assignee: Artjoms Rimdjonoks
Resolution: Fixed Votes: 13
Labels: nodata, proxy
Remaining Estimate: 0h
Time Spent: 672h
Original Estimate: 0h

Attachments: JPEG File LL.jpg     File MANY_TEMPLATES.yaml     File MANY_TEMPLATES_6.4.yaml     PNG File Screenshot 2024-12-09 at 10.01.53.png     PNG File Screenshot 2024-12-09 at 10.03.22.png     File ZBX-22580_Rust_test.tgz     Text File diff_test_ZBX-22580_10sec.diff.txt     Text File diff_test_master_10sec.diff.txt     File no_data_triggers.yaml     JPEG File nodata_triggers_resolved.jpg     Text File patch_simplify_config_cache_update.diff.txt     File zbx_export_hosts.yaml     Text File zbx_srv_proxy_incorrect_start.log    
Issue Links:
Duplicate
Sub-task
part of ZBX-23633 Service alarms storing values in wron... Closed
Team: Team C
Sprint: S24-W22/23, S24-W24/25, S24-W26/27, S24-W28/29, S24-W30/31, S24-W32/33, S24-W34/35, S24-W36/37, S24-W38/39, S24-W40/41, S24-W42/43, S24-W44/45, S24-W46/47, S24-W48/49, S24-W50/51/52/1, S25-W2/3, S25-W4/5, S25-W6/7
Story Points: 3

 Description   

Steps to reproduce:
Highloaded proxy (or proxy should be unavailable for "perceptible" period of time)
Nodata triggers (default ones, without strict parameters)
While proxy is unavailable all triggers are suppresed as they should be.
But when proxy comes up (lastseen is near 'now') it start to send collected data from the olde ones
Server process nodata trigger. Is proxy available -> yes. Is there data for (let it be) 10 min -> No, just 30 minutes old data come to the server

So problems was suppressed while proxy was unavailable, but when proxy becomes available nodata trigger fire because of proxy queue

As possible option we can set (probably configurable) period to suppress problems after proxy is available to process all queue from it. Probably there are better options

Regards, Elina

 Comments   
Comment by Guillaume ARNOUX [ 2023 Nov 15 ]

Same issue on 6.2.9.

Any update ?

Comment by Leandro Dethloff [ 2024 Mar 19 ]

Morging ,

 

Can you provide us an update about when "Prev.Sprint" will be finished ? 

 

Thanks

Comment by Leandro Dethloff [ 2024 Apr 01 ]

Morging ,

 

Can you provide us an update about when sprint will be finished ? 

 

Thanks

Comment by Leandro Dethloff [ 2024 May 29 ]

Morning ,

Can you provide us an update on this?

Thanks a lot!

Comment by Leandro Dethloff [ 2024 Jun 11 ]

Good morning, 

I am very concerned about this bug because support for version 6.4 ends at the end of the month. Several sprints have passed, and this bug has not yet been fixed. I would like to know if it will really be addressed in the current sprint because, based on the standard duration of the sprints, the one ending on the 21st would be the last opportunity for this fix to be included in version 6.4. Otherwise, it will only be fixed in version 7. This has significantly impacted my environment.

Comment by Artjoms Rimdjonoks [ 2025 Feb 05 ]

Available in versions:

Comment by Artjoms Rimdjonoks [ 2025 Feb 05 ]

Dear users, we merged the fix that we expect should greatly reduce the issue in most important use-cases. We are waiting for your feedback on how much it helps.

Comment by Leandro Dethloff [ 2025 Feb 06 ]

Thanks Artjoms and Zabbix Team for your effort in solve this bug , when 7.0.10 gets out of the oven i'll test and report my experience with the solution.

Generated at Sun Apr 20 20:56:25 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.