HTTP/S Probe Configuration in Proberix
This article will cover the detailed and comprehensive configuration options available when setting up an HTTP/S probe in Proberix.
Required Configuration
When creating an HTTP/S probe, the following fields are required:
Probe Name:
This is a friendly label that helps you easily identify the probe. The probe name will be displayed in various places within Proberix, making it easier to manage and recognize probes without relying on the full URL.
URL to Monitor:
This can be any valid URL or URI, including an IP address. You can also specify a port if needed, following the standard format (e.g., example.com:PORT). The probe will use this URL to perform its monitoring checks.
Enforce Certificate Validation (Reject Invalid):
When enabled, the probe verifies the server's TLS certificate during HTTPS requests. The probe will fail if the certificate is expired, self-signed, or does not match the hostname.
Enable Full Page Rendering:
This option simulates a full browser session, loading the entire page and all its resources. For more details, refer to the Full Page Rendering article.
Enable Change Detection:
This option tracks changes on your monitored endpoint. It's useful for detecting updates or modifications to your content. For more information, see the Change Detection article.
Method:
Choose from the most popular HTTP methods to configure the request (e.g., GET, POST, PUT, DELETE).
Request Body:
Available for methods other than GET, this allows you to configure the request body.
POST Body is JSON:
When the POST request method is selected, this option adds an additional header Content-Type: application/json to the request.
Headers:
Add as many headers as needed. The field supports typeahead, populating popular known headers, but it also accepts any text value as free input.
Response Validation
Define text patterns that must (or must not) appear in the HTTP response body. This helps ensure your site or API is returning the correct content, not just an HTTP 200.
For full details, see the Response Validation documentation.
Basic Authentication
If the URL is protected using Basic Authentication, use these fields to enter the required credentials.
General Settings
HTTP/S and TCP probes share similar general settings for monitoring intervals, locations, and how notifications are handled. These settings allow you to define how frequently probes are performed, from which geographic locations, and the configuration of alert notifications. For detailed instructions, refer to the General Settings Documentation.