HTTP Request
HTTP task shows whether the website or web service opens as you expect in normal operation.
When to use
- When you need to monitor a website page, personal account, or health endpoint.
- When it's important to check not only server availability but also correct HTTP response.
- When you want to see the failure from the user's perspective, not just by open port.
When to choose another type
- If you only need to check basic network availability of the server, Ping is often enough.
- If only certificate expiration matters, SSL is better.
- If monitoring should wait for a signal from an external process, use "External Event".
Note:
for the main check, it's better to choose a URL that truly reflects the service's operational state,
not a random page that may change due to authorization, ads, or personalization.
Common form fields
| Field | What it means | What to specify | Example |
|---|---|---|---|
| Task enabled | Determines if the check will start immediately after saving. | Leave the task enabled if you want to start monitoring right away. | Enabled |
| Name | Name of the check in the list and notifications. | Specify what exactly is being checked. | Main page example.com |
| Group | Allows assigning the task to a project or section. | Select a group if you want to keep project tasks together. | Website example.com |
| Interval | How often the HTTP check will be performed. | Choose interval based on the importance of the page or service. | 5 minutes |
| Notification channels | Where to send messages about issues and recovery. | Check the channels where you actually read notifications. | Telegram and email |
| Reports | Periodic summaries for the task. | Enable if you want an overview without manual panel access. | Weekly report |
HTTP check fields
| Field | What it means | What to specify | Example |
|---|---|---|---|
| Method | Which HTTP request will be sent. | GET is usually enough. Other methods are needed if your endpoint requires them. | GET |
| URL | Full address of the page or endpoint to check. | Specify full URL with scheme and domain. | https://example.com/health |
| Timeout | How long to wait for response before timeout error. | Choose a value slightly higher than your service's normal response time. | 30 seconds |
| Keyword | Additional content check in the response. | Specify text that must be present in the response. | OK |
| Advanced settings | Opens additional HTTP fields. | Enable only if you need headers, request body, or custom success codes. | Enabled |
| Headers | Additional HTTP request headers. | Add only headers actually needed by your API. | Authorization: Bearer <token> Accept: application/json |
| Content | HTTP request body for POST, PUT, or PATCH. | Fill if endpoint expects JSON or other request body. | {"event":"healthcheck"} |
| Success response codes | Which HTTP codes to consider normal result. | Leave standard range or set your codes and ranges. | 200-299, 301 |
| Allow self-signed certificate | Don't consider it an error if the certificate is not trusted by browsers. | Enable for internal services over HTTPS with their own certificate. | Disabled |
| Allowed check points | From which points the check will be performed. | Leave all points unless special regional or network scenario needed. | All check points |
When alert will trigger
- Site or endpoint doesn't respond in time.
- Server returns code not in success list.
- Required text missing in response if keyword specified.
- For HTTPS address, secure connection cannot be established: certificate expired, not trusted, or issued for different name. The check reason will specify what's wrong.
Checking an internal service? If it uses HTTPS with a self-signed certificate,
enable «Advanced settings» and check the «Allow self-signed certificate» parameter —
otherwise the check will fail due to certificate distrust, even though the service responds normally.
Notification settings
For each notification channel in the task, additional parameters can be set. They apply only to DOWN events.
| Parameter | What it does |
|---|---|
| Enabled | Allows or disables sending notifications via this channel for this task. |
| Delay for PRO | Delays first DOWN notification for selected time (up to 12 hours). Convenient to avoid alerts for short-term failures. |
| Repeat after PRO | Periodically repeats the notification while the task remains in DOWN status (up to 1 hour between repeats). Suitable when it's important not to miss a prolonged failure. |
The "Postpone" and "Repeat" parameters do not affect UP events and recovery notifications.