Task group
Task groups help keep checks for one project in one place and navigate the task list faster.
When to use
- When one site or server already has several checks and they need to be grouped together.
- When you want to separate monitoring by projects, environments, or directions.
- When it's more convenient to view the task list not in one flat list, but by sections.
When not to use
- If you need real availability checks. For this, choose HTTP, Ping, SSL, and other task types.
- If you have only one or two tasks and it's easy to navigate the list without grouping.
What it differs in
- The group doesn't check anything itself. It only combines other tasks.
- Disabling the group does not automatically disable nested tasks.
How to fill out the form
- Set a clear group name.
- If necessary, select the parent group.
- After saving, add the necessary check types inside the group.
Form fields
| Field | What it means | What to specify | Example |
|---|---|---|---|
| Task enabled | Determines whether the group itself will be used for notifications and reports. | Leave enabled if you want to see the group in the overall monitoring structure. | Enabled |
| Name | The group name in the task list and interface. | Specify a clear name for the site, service, or server. | Main site |
| Group | Allows nesting one group into another. | Select the parent group if you want to build a project hierarchy. | Project example.com |
| Interval | Technical form field that remains common for the task interface. | Leave a suitable default value if required by the form. | 5 minutes |
| Notification channels | Where to send messages for the group itself. | Select channels if you want to receive notifications specifically for the group. | Telegram |
| Reports | Regular summaries for the group. | Enable the report if you want to receive an aggregated overview. | Weekly report |
What will be considered a problem
The group itself does not create a separate check, so the problem occurs with nested tasks, not with the group as standalone monitoring.
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 on 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 a prolonged failure. |
The "Delay" and "Repeat" parameters do not affect UP events and recovery notifications.