[ZBXNEXT-5043] Create item to track last communication from an agent Created: 2019 Feb 14 Updated: 2020 Jan 17 |
|
| Status: | Open |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Agent (G), Server (S), Templates (T) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Change Request | Priority: | Minor |
| Reporter: | James Angi | Assignee: | Michael Veksler |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | agent, regression, triggers | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Due to the changes in timestamping items introduced in 4.0 it is no longer possible to track/trigger when an active agent client has been offline for X minutes if that client's clock is inaccurate. For example, using agent.ping.nodata(5m) doesn't work very well when the client clock is 6 minutes behind the server and its clock is used to timestamp the incoming value. In lieu of fixing the timestamps for all items for active agents I would suggest a new item like "host.lastcontact" that gets timestamped by the server every time there is communication with the host so we can properly detect offline clients. Here is a forum thread discussing this issue in more detail: https://www.zabbix.com/forum/zabbix-troubleshooting-and-problems/373803-zabbix-agent-ping-timestamp |
| Comments |
| Comment by alex dekker [ 2019 Feb 18 ] |
|
Perhaps what would be useful would be "meta-items" to track the status of items. Eg append .lastupdate to agent.ping to get the last time that agent.ping was updated. |
| Comment by James Angi [ 2019 Feb 19 ] |
|
That sounds great actually. Would actually accomplish what I was suggesting (not so eloquently) in the thread I referenced. |