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:

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.

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.

General Settings

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.

Monitoring Interval:
This setting determines how often each location will perform the check independently. For example, if you select 3 locations with a 1-minute interval, each location will conduct its checks every minute, resulting in multiple checks per minute across all locations.

Monitoring Locations:
The configuration will be dispatched to the selected locations, and probes will be conducted from those servers. These locations ensure your endpoint is monitored from various geographic regions.

Notifications

Notification Policy:
There are three options available:

• Use Existing: Select a pre-defined notification policy.
• Create New: Create a new notification policy. The UI will prompt you to configure it in the next step.
• Don’t Notify: Choose this option if you only need the probe for reporting purposes and do not wish to receive alerts. Failures will still be registered, and events will be recorded, but no notifications will be triggered.

Optional Settings

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.

Content Check

Keywords:
This feature allows you to perform an assertion of the response body with specified keywords. You can add more than one keyword.

• Any Keyword: Select this option if the search can match any of the entered keywords.
• All Keywords: Choose this option if the search must include all of the entered keywords.

Basic Authentication

If the URL is protected using Basic Authentication, use these fields to enter the required credentials.