HTTP Check
HTTP check verifies that a page or endpoint responds as expected from the user perspective.
When to use
- Monitoring website pages, control panels, or API health endpoints.
- When you care about HTTP response code and response body, not only socket availability.
- When you need an alert that reflects user-visible behavior.
When to choose another type
- For basic network availability use Ping.
- For certificate expiration use SSL.
- For external task completion, use External Event.
Tip:
Choose a URL that reflects real service health, not a random page that may be protected or dynamic.
Common fields
| Field | Meaning | What to enter | Example |
|---|---|---|---|
| Enabled | Whether the check runs after saving. | Enable if you want immediate monitoring. | Enabled |
| Name | Display name in task list and notifications. | Specify what exactly is being checked. | Main page example.com |
| Method | HTTP method used in the request. | Use GET in most cases. | GET |
| URL | Exact endpoint to request. | Always set full URL including scheme. | https://example.com/health |
| Timeout | Response timeout before marking as issue. | Set slightly above average response time. | 30 seconds |
| Expected keyword | Additional check for response body. | Set a stable text that must be present in response. | OK |
| Notification and report settings | Where alerts and reports are sent. | Use channels where you always receive notifications. | Telegram + email |
When it becomes an issue
- Response is too slow and exceeds timeout.
- HTTP status is outside expected set.
- Keyword is not found when configured.