Advanced Monitor configuration
Configure accepted statuses, schedules, timeouts, redirects, headers, queries, and request bodies while preserving PointWarden's public-target and sensitive-value boundaries.
Use advanced request settings when the default GET request from the Owner quickstart does not describe the Endpoint you control. A Workspace Owner or Admin can change these settings.
Request behavior and limits
| Setting | Supported behavior |
|---|---|
| Accepted statuses | HTTP 100 through 599 as exact values or ranges |
| Schedule | Every 1, 5, 15, 30, or 60 minutes |
| Timeout | One total request budget from 1 through 30 seconds |
| Custom headers | Up to 20 unique safe headers and 16 KiB combined |
| Request body | POST or PUT only, up to 64 KiB of UTF-8 |
Enter accepted statuses as comma-separated exact values or ranges, such as 200-299, 304. PointWarden normalizes overlapping ranges. A Check passes only when final response headers arrive within the total timeout and the final status is accepted.
The timeout covers the complete attempt, including public DNS validation and every followed redirect. The schedule controls regular Scheduled Checks; confirmation Checks may run sooner when PointWarden is confirming an Incident or Recovery. See Check types for the effect of each Check.
Public targets and redirects
The Endpoint must be an absolute public HTTP or HTTPS URL. HTTP uses port 80 and HTTPS uses port 443. PointWarden rejects embedded user information, fragments, nonstandard ports, and hosts or resolved addresses that are private, loopback, link-local, reserved, multicast, metadata, or otherwise non-public. It repeats public-address validation before every Check.
GET and HEAD may follow at most five redirects. PointWarden validates every hop as another public HTTP or HTTPS target on its standard port before sending the next request.
An invalid redirect location, a non-public redirect target, or a sixth redirect produces a Failing Check. A redirect response without a location is final and passes only when its status is accepted. All followed requests keep the configured GET or HEAD method.
POST and PUT never follow redirects or rewrite their method. A redirect response is final and passes only when its status is accepted; both methods require the repeat-safety acknowledgement because Scheduled Checks may retry the same request.
Sensitive request values
The visible Endpoint projection includes the scheme, host, standard port, and path. When a query exists, PointWarden replaces its values with ?•••.
Keep secrets out of the visible path. Put credentials or tokens in the query, a permitted request header, or a POST or PUT body instead.
Saved query values, header values, and request bodies are encrypted and unavailable to normal product views.
| Configuration | What a Workspace Member can see after saving |
|---|---|
| Endpoint | Scheme, host, standard port, path, and a masked query marker |
| Query values | Never disclosed; the complete URL remains encrypted |
| Headers | Names appear only on the management page; values are never disclosed |
| Request body | Only its presence is shown; its saved content stays encrypted |
Header names must be valid, unique without case differences, and free of PointWarden-controlled transport headers such as Host, Content-Length, User-Agent, proxy headers, and X-Forwarded-*. Header values cannot contain line breaks. Request bodies are available only for POST and PUT.
Verify the configuration
Run Test Request before saving when you need immediate diagnostic evidence. It validates the unsaved public target and request behavior but does not change Availability, Incidents, Availability Rollups, or Notification Events.
If the request fails, troubleshoot a failed Test Request or Check. Before changing an existing Monitor, review how to modify and manage its lifecycle.