[ZBX-15942] Caveat with value throttling: queue statistics show real update time, not poll time Created: 2019 Apr 04 Updated: 2020 Mar 23 Resolved: 2019 Oct 29 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Proxy (P), Server (S) |
Affects Version/s: | 4.2.0 |
Fix Version/s: | 4.2.4rc1, 4.4.0alpha1, 4.4 (plan) |
Type: | Problem report | Priority: | Minor |
Reporter: | Alexey Asemov | Assignee: | Zabbix Development Team |
Resolution: | Fixed | Votes: | 3 |
Labels: | preprocessing, queue | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: | custom_autoincrement_step.diff | ||||||||||||||||
Issue Links: |
|
||||||||||||||||
Team: | Team A | ||||||||||||||||
Sprint: | Sprint 51 (Apr 2019), Sprint 52 (May 2019) | ||||||||||||||||
Story Points: | 1 |
Description |
There is a caveat with preprocessing of change throttling (update when changed / update when changed with heartbeat). We've started using that for multiple items, with 'heartbeat' interval of hours up to entire day. Queue display started showing all such items in above 10 minutes. While it's correct because item was not actually updated for long (no changes), it is totally misleading, because item was actually polled, and looks like there is some polling problem (indistinguishable from polling issues). The solution to distinguish between throttling and polling issue on queue view can be recording actual poll time for the item instead of the update time, and using this poll time for queue view display. |
Comments |
Comment by Elina Kuzyutkina (Inactive) [ 2019 Apr 05 ] |
|
Comment by Glebs Ivanovskis [ 2019 Apr 05 ] |
Maybe this only affects items monitored by proxy? |
Comment by Alexey Asemov [ 2019 Apr 05 ] |
Hello, Indeed, I confirm this happens only on items that are monitored by proxy. Can't repeat on 'local' items either. |
Comment by Alexey Asemov [ 2019 Apr 05 ] |
I also confirm it's certainly not a polling issue per se, throttling heartbeat works nicely. |
Comment by Andris Zeila [ 2019 May 29 ] |
Released
|
Comment by Alexey Asemov [ 2019 Jun 27 ] |
I confirm it works fine. Thanks a lot for fixing this, it was really a big deal in my case |
Comment by Yanda Andrey [ 2019 Oct 29 ] |
Hello, This release broke zabbix proxy in some environments. For example, proxy cannot send more than 10 records per connection if auto_increment_increment > 1. |
Comment by Yanda Andrey [ 2020 Mar 23 ] |
I tried to fix this issue for me and I can share my tries. This workaround can be not optimal but I hope it could help someone. |