We have a datasource that pings a network device. The script runs on the server closest to the network device. We then have a monitor type that reacts to the property Bag collected by the datatsource. Then the monitor that uses the monitor type to monitor the network device.
The monitor runs every 2 min and if the is no reply for 3 consecutive samples we alert.
Our consern is the timeout of the datasource script. The monitor runs every 2 min and best practice says that the timeout should be set to 5 min. So if somthing happens and the script has not completed after 2 min we are going to have another instance of the script running. We could have a total of 3 scripts running at the same time.
Is this going cause any problems?
We currently have the timeout set to 60 sec and all is well but we want to stick with best practice as far as possible.
Thanks
Robert
Hi, just tested it with a simple script. Write to eventlog, wait 180 seconds. Interval was 60 seconds. But it only writes every 180 seconds into the eventlog, therefore the script won't run parallely. But, it doesn't make any sense to on one hand stick with the Best Practice for the Timeout, but on the other hand take an interval that is lower than the timeout. Conclusion: Interval must not be lower than Timeout
EDIT:
I tested this using a Powershell Write Action module, therefore I can't guarantee that this will work the same way using vbs.