[ZBXNEXT-1022] heartbeat communication for between Zabbix server and agent Created: 2011 Nov 08 Updated: 2014 Nov 08 |
|
Status: | Reopened |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Agent (G), Server (S) |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | New Feature Request | Priority: | Major |
Reporter: | Kodai Terashima | Assignee: | Unassigned |
Resolution: | Unresolved | Votes: | 5 |
Labels: | heartbeat | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
Description |
Zabbix agent status on Zabbix server has some problems at the moment.
I think it's good that Zabbix server and agent communicate using exclusive heartbeat connection periodically. |
Comments |
Comment by richlv [ 2011 Nov 08 ] |
hmm. usual suggestion is to avoid using 'status' item and use agent.ping + nodata() instead - that should solve this issue |
Comment by Kodai Terashima [ 2011 Nov 08 ] |
I know agent.ping + nodata() solution, but the solution don't solve the first problem And, I think check of agent availability is important, but agent.ping + nodata() is difficult for Zabbix beginners. |
Comment by richlv [ 2011 Nov 08 ] |
in latest versions userparameters going down still should result in nodata() trigger for agent.ping. would that solve the problem ? continuing with slow hosts as usual is not feasible, as they would hamper the overall monitoring - such userparameters should be fixed/changed |
Comment by Oleksii Zagorskyi [ 2011 Nov 09 ] |
Kodai, about "if any user parameter item take a long time, Zabbix server stop monitoring all of other item on same host" But this feature request is very interesting overall. |
Comment by Kodai Terashima [ 2011 Nov 09 ] |
Thank you pointing that out, Oleksiy. first problem I wrote looks same problem as I think heartbeat communication between server and agent (and unreachable host is handled by heartbeat) improve the problem and usability so much. |
Comment by Peter Schultz [ 2011 Nov 09 ] |
...Only one "slow userparameter or check" affect to all of other items on same host. I think it is not good behavior. Zabbix server should only change item status to not supported in this case. ... agreed !!! |
Comment by missing [ 2012 Nov 03 ] |
i had this problem yet,i found something funny that zabbix server will check that server after aboute 320 minutes again. |
Comment by Strahinja Kustudic [ 2014 Nov 08 ] |
Zabbix setting a host as unreachable just because one item is bad, is the most annoying thing. The biggest problem is that it makes Zabbix unreliable, because if one item times out, the whole host gets disabled, so it stops running other items on that host, which means the host is not being monitored properly. I think the easiest way to solve this problem is to define items which can make a host unreachable, e.g. it could be a check box in the item create/edit page called "Make host unreachable on time out", or some better name. This way e.g. agent.ping could have that checkbox set and only that item would make the host unreachable. |
Comment by richlv [ 2014 Nov 08 ] |
that's a different problem which is tracked at |
Comment by Strahinja Kustudic [ 2014 Nov 08 ] |
Well it's not a different problem, they are related, since both of them would change how we detect if a host is unreachable. |