Greetz,
So I watch a lot of devices on my network backhauls and access points (like a good network nerd does) but.. I was starting to go crazy with some devices that were pretty far out there on my network, because my alerts to my phone were every few mins to every few hours nothing was making sense. Not all of my netwatch alerts were getting triggered. I know that some may have a capacity or a port flap issue that may trigger the netwatch so I up’d the timeout on some of the netwatches. I then noticed that all of my netwatches that had an absurd amount of timeout were the only ones that were getting possibly falsely triggered.
Here is the numbers: If your timeout is set to 100000 or greater than it will randomly present a false trip. Where as if you have the timeout set to 10000 there is a good chance you numbers will over look a ping lag and hum a long until something serious happens. If the netwatch is too low then every capacity spike that causes a longer than usual lag you will get an alert tripped.
I have no idea why a longer timeout would cause this issue. Maybe the number counters get overlooked or confused between the counts on the netwatches?
Any ways this was something I had observed and I just wanted to share to the other Mikrotik folks out there.
-Cheers,
DesertAdmin