Q: I have IPNetwork installed and running, but how can I be sure it’s running and monitoring is active?
A: To make sure IPNetwork installation is actually active, monitoring service is running and monitoring performed, you need to monitor IPNetwork installation itself. Otherwise, if it fails, you have no clues on whether monitoring is actually in progress.
The simplest approach is to install IPNetwork on another computer (so that the computer with primary IPNetwork installation could be directly connected) and create Windows Service monitor checking for presence of IPNetwork monitoring service.
On third step of New Monitor Wizard, enter service name “IPNetwork Monitor” (without quotes; make sure you specify proper credentials and leave no extra white space in service name):
Set reasonable polling interval and alerting. After that, if you have primary IPNetwork installation monitoring service gone down, you will be notified and can react promptly.
Note that you should monitor, exactly for the same reason, that auxiliary IPNetwork installation is active (otherwise, you have no guarantee the health of primary IPNetwork could be checked). The simplest solution is to monitor it from IPNetwork primary installation, using the same approach.
If you can install more than single auxiliary IPNetwork installation, then make sure every one of those monitors both primary installation and other auxiliary installation(s) in the manner mentioned above (and make all auxiliary ones monitored from IPNetwork primary installation). If at least one of auxiliary installation is outside the primary’s network and uses alternate Internet connection, you still rise chances the primary IPNetwork monitoring service shutdown won’t remain unnoticed.
Related links
Check out our Knowledge Base where we answer questions regarding various topics. If the primary monitoring service stops, it cannot alert about its own failure. A separate IPNetwork installation can watch the primary service and send alerts when it goes down. Use a Windows Service monitor from another computer and set the service name to IPNetwork Monitor, with the correct credentials and no extra spaces in the service name. Yes. The auxiliary installation should be monitored as well, commonly by the primary installation or by another auxiliary installation, so its own failure does not go unnoticed.
Frequently Asked Questions
Why monitor an IPNetwork installation from another installation?
Which monitor can check that IPNetwork Monitor is running?
Should the auxiliary IPNetwork installation also be monitored?