[ZBX-13616] As Trapper processes adjust monitoring time, trigger evaluations use incorrect data Created: 2018 Mar 15 Updated: 2018 Mar 15 Resolved: 2018 Mar 15 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Proxy (P), Server (S) |
Affects Version/s: | 2.2.22rc1, 3.0.15 |
Fix Version/s: | None |
Type: | Incident report | Priority: | Trivial |
Reporter: | MATSUDA Daiki | Assignee: | Unassigned |
Resolution: | Duplicate | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
Description |
Zabbix Server and Proxy Trapper processes receive data from Agents and Proxies. Then they adjust monitoring time with included timestamp. The data from Agent, especially log or eventlog, is sent by big block. But from Proxy, is sliced in spite of reading log almost same time. By this, in a Agent reading Proxy receiving Send data 1 and 2 separately Server receving The revert occures. In addition, the trigger with regexp() selects data with the accuracy second not nano second. So, when trigger evaluates against data 2, select data 1 because it selects the latest data. |
Comments |
Comment by Glebs Ivanovskis (Inactive) [ 2018 Mar 15 ] |
Good news: timestamp corrections will be removed in I'm going to close this issue as Duplicate, but anyway, thank you for reporting it! |