With PRTG 22.x.80, you migrated the Cloud v1 sensors. What do I need to know?
What do I need to know about the migration of the Cloud v1 sensors?
Votes:
0
1 Reply
Accepted Answer
Votes:
0
This article applies as of PRTG 22.x.80
Cloud v1 sensor migration
With PRTG 22.x.80, we discontinued the Cloud HTTP sensor and the Cloud Ping sensor. Any Cloud HTTP sensors and Cloud Ping sensors in your network were paused and a Cloud Ping v2 sensor and Cloud HTTP v2 sensor were automatically added to the corresponding device. See below to find out about any potential changes and unusual behavior.
- If the sensor receives a Connection Reset error code, it automatically retries the request. Some servers have a limited connection pool. This causes connections to break while requests are being processed.
- Not all servers send the correct error code when a connection times out. The Connection Aborted error is therefore mapped to a Request Timeout (HTTP status code 408).
- The Cloud Ping v2 sensor and the Cloud HTTP v2 sensor accurately measure the response time and are consequently more sensitive to network changes. Any change can cause timeouts or spikes. To mitigate these problems, try to increase the timeout of the sensors. If you run into any of the abovementioned issues or anything else, please get in touch with us.
More
Why do the Cloud HTTP and Ping Sensors return an error now?
What sensors are deprecated and what are their successors or alternatives?
Last change on Jun 13, 2023 12:43:51 PM by
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.
Add comment