Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > ipMonitor > ipMonitor - Knowledgebase Articles > Troubleshoot connection issues with ipMonitor HTTP-based monitors

Troubleshoot connection issues with ipMonitor HTTP-based monitors

Updated September 21, 2018

Overview

This article provides information about the HTTP-based monitors in ipMonitor and how to troubleshoot connection issues.

Environment

All ipMonitor versions

Detail

HTTP-based monitors within ipMonitor

Monitor Description
HTTP Connects to the IP address or domain name specified within the monitor, requests root (“/”), and disconnects.
HTML/ASP Connects to the IP address or domain name specified within the monitor, requests the specified URL, verifies for a specific string of text within the response, and disconnects.
HTTPS Performs the same function as the HTML/ASP monitor over SSL.
HTTP User Experience

Connects to the IP address or domain name specified within the monitor, requests the specified URL, and calculates a checksum on the received file.

All subsequent tests compare the checksum with the original checksum gathered. If the checksums are different, the monitor will fail.

Do not use this monitor for dynamic pages such as ASP and CGI.

Troubleshoot connection issues

  1. Gather the IP address / domain name, TCP port, and URL values from the failing monitor.
  2. On the ipMonitor system, open a CMD window and enter the following command:
    telnet [IP Address/Domain Name] [TCP Port]
  3. When connected to the website, enter the following commands.
    • For the HTTP monitor:
      GET / HTTP/1.0
      Host: [IP Address/Domain Name]
    • For the HTML/ASP monitor and the HTTP User Experience monitor:
      GET /[URL] HTTP/1.0
      Host: [IP Address/Domain Name]
  4. Within the response, make sure that the HTTP status code returned is between 200 and 399. If the monitor is configured to look for text, verify that you can see the searched text within the response.

Debug feature

You can also troubleshoot connection errors using the Debug feature.

  1. Click the monitor name.
  2. In the Edit Monitor window, append "debug" to the end of the URL displayed in the browser, and then press Enter.
    Debug displays in the top gray menu.
  3. Click Debug and view the communication records between the ipMonitor system and the website.

Install Telnet on Windows

To install Telnet on Windows, see Install Telnet Client (© 2017 Microsoft, available at https://technet.microsoft.com/, obtained on August 15, 2015).

 

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Last modified

Tags

Classifications

Public