Open port
Port check answers the question whether it is possible to establish a connection to the required service on a specific port.
When to use
- When it's important to understand if SSH, SMTP, database, or another service is available on the required port.
- When Ping is uninformative or disabled, and HTTP is not suitable for the service.
When to choose another type
- If it's important to check a website page or API, use HTTP.
- If you only need the certificate expiration date, SSL is better suited.
Form fields
| Field | What it means | What to specify | Example |
|---|---|---|---|
| Name | Name of the check. | Specify which service or port you are monitoring. | HTTPS on main server |
| Group | Allows assigning the task to a project or section. | Select a group if you want to keep project tasks together. | Main project |
| Host | Server where the service should be available. | Specify domain name or IP address. | mail.example.com |
| Port | Service port number. | Enter exactly the port that should be available. | 443 |
| Timeout | How long to wait for connection before error. | Choose a value with margin for typical network delays. | 10 seconds |
| Interval | How often to check the port. | Choose frequency based on service criticality. | 5 minutes |
| Allowed check points | From which points the port can be checked. | Leave all points if special check geography is not needed. | All check points |
| Notification channels | Where to send messages about issues and recovery. | Check channels where you actually read notifications. | Telegram and email |
| Reports | Periodic task summaries. | Enable if you want to receive an overview without manual panel access. | Weekly report |
When the alert will come
The alert will come if the connection to the port fails or does not establish within the timeout.
Notification settings
For each notification channel in the task, you can set additional parameters. They only apply to DOWN events.
| Parameter | What it does |
|---|---|
| Enabled | Allows or prohibits sending notifications through this channel for this task. |
| Delay by PRO | Delays the first DOWN notification by the 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 prolonged failures. |
"Delay" and "Repeat" parameters do not affect UP events and recovery notifications.