[ZBXNEXT-840] if some snmp values timeout, the whole host doesn't get snmp values Created: 2011 Jul 08  Updated: 2014 Apr 12  Resolved: 2014 Apr 12

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: None
Affects Version/s: 1.8.4
Fix Version/s: None

Type: Change Request Priority: Major
Reporter: matthias zeilinger Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: snmp, timeout
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

server 1.8.4, agents 1.4.6


Issue Links:
Duplicate
duplicates ZBX-4284 Possible wrong host (agent!,snmp?) di... Closed

 Description   

i´m monitoring many jboss´ on one host. on each jboss i´m collecting snmp values.
if one jboss is down and the snmp values are not responsive, the complete host doesn´t collect any snmp values.



 Comments   
Comment by richlv [ 2011 Jul 08 ]

that does seem to be "works as designed" - if snmp timeouts, zabbix decides that snmp on the host is not available.
doing otherwise would create huge performance problems.

not sure what could be an approach that could work here

Comment by matthias zeilinger [ 2011 Jul 19 ]

but why zabbix doesn´t change the item status to "not supported" for the affected items after some time, so all other snmp-values can be collected again.
i can´t understand, why zabbix disables the complete snmp-values for that host.

Comment by richlv [ 2014 Apr 12 ]

ZBX-4284 talks about & suggests some algorithm for detecting "bad" items - closing as duplicate of it

Generated at Fri Mar 29 10:18:50 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.