The NT_ServiceDown Knowledge Script can generate a number of ‘false’ service down alerts following a server reboot. This occurs if the Job executes before the server has completed rebooting and monitored services have yet to start. In order to address this behaviour I have modified the KS to include two additional parameters under General Settings:
·Don’t monitor services following reboot?
oMinimum uptime before commencing monitoring
If the first parameter is enabled then the KS gets the value of the System Uptime performance counter and compares it to the threshold in minutes defined in the second parameter. If it’s below the threshold it causes the KS to exit gracefully without monitoring any services. Once server uptime exceeds the threshold, service monitoring commences as normal.
Note: this modification has been made to version 7.6.276 of the KS.