Ad Widget

**richlv** · 13-08-2011, 11:47

apparently it doesn't always take 17 seconds... also, that means you have increased default server timeout fairly significantly, which can lead to other problems.

i'd suggest sending values from that script using zabbix_sender, or maybe writing them to temporary files and then picking up with zabbix - the first would involve less steps, but wouldn't give you exact intervals. latter would give exact intervals, although actual value retrieval time would be a bit off.

**mbrijun** · 13-08-2011, 12:26

Hi Rich,

thanks for reply, I will look into the zabbix_sender solution.

Martynas

**mbrijun** · 13-08-2011, 15:02

a crontab entry that combines my script with the zabbix_sender does the job perfectly.

i'd suggest sending values from that script using zabbix_sender, or maybe writing them to temporary files and then picking up with zabbix - the first would involve less steps, but wouldn't give you exact intervals.

why would it not give exact intervals? It runs precisely when crontab tells it to.

**richlv** · 13-08-2011, 17:15

Originally posted by mbrijun

why would it not give exact intervals? It runs precisely when crontab tells it to.

if a script takes 17 seconds to execute, i suspect that time might vary a bit. the value would only be sent when the script finishes, of course, so there might slight drift around those 17 seconds

Ad Widget

Irregular firing of external check

Irregular firing of external check

Comment

Comment

Comment

Comment