Tue Aug 15, 2017 4:10 pm
if this is really the place of requests, then bring 'em on - i guess at least this could be in par with the "regular" ping command
- packet size (in bytes)
- df-bit-set
- log (log the "comment" and the state change (down,up))
yes, i know, one can just poke in a one-liner to log the outcome as down/up-script, but do we really need to do this manually?
btw, when we are there with scripts, it would be handy to know on which entry points which environment values are exposed to the user.
i kinda could think of "comment" and "host". or if i let my mind fly away, then i'll add "number-of-probes", so netwatch would send X consecutive ICMP echo requests, then report back the success rate or successfully received replies, and one could specify a "threshold" value to judge whether the target is reachable or not. and in this case the script could receive "probes_sent" and "probes_received"
even the current operation could be mapped to this: number-of-probes=1 threshold=1
and there we almost have cisco's RTR/SAA