-
Problem report
-
Resolution: Fixed
-
Major
-
3.4.2, 4.0 (plan)
-
None
-
CentOS7 + 3.4.2 Server with MariaDB + 3.4.3 Proxy with Sqlite3
-
Sprint 19, Sprint 20
-
0.5
Steps to reproduce:
1. Make sure you have your Proxy in active mode
2. Check the HeartbeatFrequency= parameter.
3. Add host to be monitored by proxy
4. Add an item with the Update interval less than HeartbeatFrequency value.
5. Observe the results under Monitoring -> Proxy tab.
6. Compare the observations from Monitoring -> Proxy with the Last 500 Values tab for tested item.
Result:
Last seen will be updated only when the next Heartbeat message would be sent.
Expected:
Last seen needs to be updated as fast as new bunch values will came in.
P.S. - Behavior is the same for both - Zabbix Agent Active and Passive item checks.
- causes
-
ZBX-13153 Not reliable proxy last access update
- Closed
-
ZBX-13755 Proxy last access is not updated on 32 bit Zabbix server
- Closed
- part of
-
ZBXNEXT-936 Zabbix Proxy does not proxy remote commands
- Closed