HTTP 122 Sensor triggering errors but site is up and running with no issues.

Modified on 2025-06-10 12:43:52 +0200

I am having an issue with one of our sites. I am currently monitoring one of our sites with the HTTP 122 sensor. The site is up 100 percent of the time, however, the sensor is reporting a 25 percent downtime over a 30 day period. There has been no actual downtime on the site at all. I do see some socket errors in the logs. Could it be that I am using the wrong type of sensor? I'm not getting anywhere with the hosting site because the site is up so they feel as though there is no issue. I just want to understand the underlying issue here and what I can do to fix it. Please Help

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Is it possible this was a DNS issue? Can you run a report on the sensor to hone in on the period of time that the sensor showed an error, and then give me the error the sensor produced?

Jun, 2018 - Permalink

Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.

HTTP 122 Sensor triggering errors but site is up and running with no issues.

Article CommentsAttention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Search

Attention

Related Articles

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.