Group & Manual monitors
Two special monitor types help you model higher-level services.
Group
A Group monitor rolls several child monitors into a single status. Use it to represent a
whole service made of parts — for example an "API" group that is DOWN if any critical
dependency is down.
- The group's status is derived from its members.
- Great for keeping the status page readable: show one line for "Checkout" instead of five underlying checks.
Manual
A Manual monitor has no automated checks — you set its status yourself. Use it for components you track operationally but can't probe automatically, or to force a state during an event.
| Type | Automated? | Typical use |
|---|---|---|
| Group | Derived from members | Aggregate a service's sub-checks into one component. |
| Manual | No — set by hand | Third-party dependencies, human-judged components. |
Note
You can combine these with real checks: e.g. a Group called "Payments" containing an HTTP / API check on the payments API and a Manual entry for your upstream payment provider.