I am running a discovery process for an adaptec controller that keeps going unsupported. It is doing this due to what I believe is a timeout. I know I can adjust the global timeout setting in the zabbix server config, but I really do not want to do that as I am concerned that other metrics like slow SNMP or sustem.run commands that are poorly configured could slow down the poller processes. I have confirmed that my current setting is set to 3 000 milliseconds (3 seconds) and the arcconf command that my discovery is running (agent side) is occasionally taking longer than 3 seconds.
Is there a way to add a wait for that specific discovery key so that the system knows it can wait longer than 3 seconds for that specific result? Perhaps define it as an agent side (agent active) initiated call instead of a server side call?
Carl
Is there a way to add a wait for that specific discovery key so that the system knows it can wait longer than 3 seconds for that specific result? Perhaps define it as an agent side (agent active) initiated call instead of a server side call?
Carl