ipMonitor includes a Debug feature that allows you to view the web server response received by any HTTP Monitor. This is especially useful when trying to diagnose the reason for a Monitor failure, especially if your Internet browser shows that all configuration settings are correct.
The HTML / ASP Monitor is configured to follow redirects to a specific URL and search for the word "internal".
The Monitor fails to find the specified word, even though the "internal" text string clearly appears when the page is viewed with Internet Explorer or a similar browser.
To use the Debug feature, proceed with the following:- Log in to the ipMonitor Administration web interface.
- Click the Monitors menu option.
- Click the name of the specific HTML/ASP Monitor to arrive at its settings.
- Add the word 'debug' to the end of the URL in your web browser's address bar.
- Press Enter while your cursor is still in the URL address bar. On the second row of the navigation menu, you should now see a new button labeled Debug. Click the Debug button to view the resulting output.
Examining the web server response received by the HTML/ASP Monitor allows you to diagnose the cause of the Monitor failure. In this instance, you may find that the "internal" text string the Monitor is searching for does not appear in the output received from the Debug feature. The problem may likely be caused by additional content being retrieved by a script embedded in the page, which is not rendered by the HTML/ASP Monitor.
The Debug output file is generated in .txt format and can be immediately opened with a text editor such as Notepad, or saved to disk for later analysis. By default, the file is named debug.txt.
For information on other features and concepts related to those discussed in this article, refer to the following ipMonitor resources:
< Back
Last Updated: April 17, 2006 | What did you think of this topic?