Support servername and connect (SNI) in http sensors
Modified on 2025-06-10 15:30:35 +0200
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.
Important: We no longer maintain this article. The information might be out of date.
When monitoring a website from behind the firewall and load balancer we monitor each website that answers with a FQDN that lists' its public IP address. For example we may have five web servers all hosting abc.com in the IP range 172.20.0.0/16. While abc.com may resolve to 1.1.1.1 we need to query each server on the 172.20.0.0/16 network to check on the health of each web server and their ability to load the website properly.
It would be great to have the HTTP sensors to support two fields:
servername: internal DNS name or IP address of a server to monitor
connect: the FQDN the HTTP sensor should submit to the servername to load the website.
This way we can test the same FQDN on each web server internally.
Article Comments
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.
Hi there,
This sounds like a feature request. If you want to submit a new feature, please follow these steps: https://helpdesk.paessler.com/en/support/solutions/articles/76000063572-how-can-i-propose-new-features-or-sensors-for-prtg
Aug, 2020 - Permalink