[ZBXNEXT-6445] Fix flapping of "System time is out of sync" trigger Created: 2021 Jan 17 Updated: 2024 Jul 01 Resolved: 2024 Jul 01 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Templates (T) |
| Affects Version/s: | 5.0.7, 5.2.3 |
| Fix Version/s: | 6.0.32rc1, 6.4.17rc1, 7.0.1rc1, 7.2.0alpha1 |
| Type: | Change Request | Priority: | Trivial |
| Reporter: | Evren Yurtesen | Assignee: | Denis Rasikhov (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Team: | |
| Story Points: | 0.3 |
| Description |
|
This is NOT a request about the seconds set for this trigger. The default setting uses {$SYSTEM.FUZZYTIME.MAX} which is 60s and it is OK/FINE! The problem is flapping when the system time is out of sync and close to trigger check value. In my screenshot the {$SYSTEM.FUZZYTIME.MAX} was set to 30s The problem is that when system time difference is near 30s. Zabbix starts receiving values like 29s, or 31s depending on network conditions. This is causing flapping of this trigger. Please introduce hysteresis! -> https://blog.zabbix.com/no-more-flapping-define-triggers-the-smart-way/1488/ Again, this issue is NOT related to value of {$SYSTEM.FUZZYTIME.MAX}. It is related to flapping condition for trigger! I tried to make a bug report for this issue. But it was closed with a strange comment unrelated to the issue I reported.
|
| Comments |
| Comment by Evren Yurtesen [ 2021 Jan 25 ] |
|
|
| Comment by Denis Rasikhov (Inactive) [ 2024 Jun 20 ] |
|
Fixed in:
|