Historically weâve used the NTService check for monitoring windows services that could not respond on a given port. However as there was a third-party library involved, it was less than responsive to the timeout parameter and at times run upwards of 20-seconds per check. Does the NTProcess check use the same library and is it bound to the same restrictions?
Thanks, ~Patrick To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.
