I'm regarding about testing a machine supposed to stay close, based on ping monitor.
I tried to setup with no success. I changed critical options for both settings. I put one by one the setting but same result.
I don't understand because it's clearly the same result that I caught with my critical triggers, the only thing is possibly the decimal variation, I suspect 100.0 is not exactly the same as 100 or more believable, I think the ping is not going on triggers, because it's fail before, so this is why the caption give me a CRIT.
So if anyone have a solution, with a different test, I'm all open.
In reply to Robert Vandervoort:
In reply to adminNotarius:
I think the easiest way would be to use the custom script monitor. When you add a new service monitor, go to the very bottom under "advanced and custom" section. Select "Custom" and continue.
Then set it against that element you're trying to ensure stays down. Give it a name, description, and then in the "Script Name" field put the path to your uptime\scripts folder like so
/program files/uptime software/uptime/scripts/pingcheck.bat
Now we need to drop a batch file in that folder, called, pingcheck.bat. Feel free of course to put this stuff wherever you see fit and call it whatever you iike, just make sure it all matches up. Contents of the bath file are:
ping -n 1 %1
Then, back in the service monitor you are creating, for the "Arguments" field, put:
Lastly, in the critical status section, choose
Critical [does not contain] Destination host unreachable
Destination host unreachable
Now save it... When you get back to the parent page, hit test. What this is going to do is call the ping command and try a single time to reach the host this service monitor is assigned to. It will output the standard ping output and we are checking to be sure it says the host is unreachable. If it does NOT say that, it will trip the critical state.
This is a good intro actually to creating custom script monitors. You can use them to accomplish all kinds of things and creating them really is this easy. Note the format of the script path, that's the only tricky part here! don't be tempted to use something like C:\program files.... it will not work.
You may find these links helpful too. First, a list of all the variables we can use, like %UPTIME_HOSTNAME%
And of course the doc for creating custom monitors.
Let us know if there is anything else we can help with!
Well, you might just consider leaving it as the default setup without the new monitor, and not alerting on crit for the ping, but instead only alert on recovery of the ping. Then whenever the element in question comes online the other monitors will start working and you'll get an email that the element came back online. Now, the new monitor we just created will be critical, and that would be responsible for continuing to alert you that the element is up, getting your attention.