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.
  • A disabled group pauses everything nested in it: tasks and groups inside are not checked until the group is enabled.
  • The tasks inside a disabled group remain enabled. You can configure and enable them in advance, then run everything at once by enabling the group.
  • Groups can be nested no deeper than 5 levels.

How to fill out the form

  1. Set a clear group name.
  2. If necessary, select the parent group.
  3. After saving, add the necessary check types inside the group.

Form fields

Field What it means What to specify Example
Task enabled An enabled group monitors nested tasks, sends notifications and reports. A disabled group pauses everything nested in it. Leave enabled for tasks inside to be checked. Disable to pause them all at once. 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, no deeper than 5 levels. Select the parent group if you want to build a project hierarchy. Project example.com
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. The group transitions to DOWN as soon as at least one task or group inside it goes DOWN, and returns to UP when all of them recover.

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.
To task types list