Group Monitor
Combine multiple monitors into a weighted aggregate status
Group monitors aggregate member monitor status and latency into one monitor.
Minimum setup
Requirements from current validation:
- at least 2 member monitors
- members must be active, non-group monitors
- weights must sum to approximately
1(tolerance0.01) executionDelaymust be>= 1000mslatencyCalculationinAVG | MAX | MIN
Status scoring model
Member statuses are normalized to a 0–1 scale:
UP = 1DEGRADED = 0.5DOWN = 0
Members in MAINTENANCE are treated as UP (score 1) and do not affect the group status.
Weighted score:
Σ(member.weight * statusScore)
Mapped group status:
= 1→ UP (all members healthy)> 0and< 1→ DEGRADED (partial failure)= 0→ DOWN (all members down)
Example
5 monitors with equal weight (0.2 each), 1 is DOWN:
4 × 0.2 × 1 (UP) + 1 × 0.2 × 0 (DOWN) = 0.8 → DEGRADED
Latency aggregation
Group latency uses selected mode:
AVG: average member latencyMAX: slowest member latencyMIN: fastest member latency
Execution delay
executionDelay (in milliseconds) controls how long the group monitor waits before running its aggregation. This delay gives member monitors time to complete their own checks and update the cache before the group reads their statuses.
- Default:
1000(1 second). Minimum:1000. - If member monitors take longer to finish (e.g. slow API checks), increase this value so the group always reads fresh results.
- Only affects cron-driven execution. When a member's status is updated via the API, the cache is updated immediately and the group will read the new value on its next run.
Member display
memberDisplay sets what the Included Monitors button does on status pages and on the monitor page. In the group monitor's settings, this field is Member Display.
DRAWER: opens the member list in a panel at the bottom of the screen. This is the default.INLINE: slides the member list open below the group on the same page. In a grid layout, the list opens inside the group's cell. In thecompact-gridlayout, member rows hide their status bars, like the group row.
Configuration fields
| Field | Type | Default | Notes |
|---|---|---|---|
monitors |
Array<{tag, weight}> |
[] |
Required, min 2 |
executionDelay |
number |
1000 |
ms to wait before aggregating; must be >= 1000 |
latencyCalculation |
AVG|MAX|MIN |
AVG |
|
memberDisplay |
DRAWER|INLINE |
DRAWER |
How the member list opens on public pages |
Example
{
"monitor_type": "GROUP",
"type_data": {
"monitors": [
{ "tag": "api", "weight": 0.6 },
{ "tag": "db", "weight": 0.3 },
{ "tag": "cache", "weight": 0.1 }
],
"executionDelay": 1500,
"latencyCalculation": "AVG"
}
}
Troubleshooting
- Cannot save: verify weights sum to
1, min member count, and delay >=1000 - Unexpected stale status (cron): increase
executionDelayso member checks finish before the group aggregates - Unexpected stale status (API updates): ensure you are running a version that updates the cache on API writes — older versions only updated the cache from cron, causing the group to miss API-driven status changes
- Group too sensitive/lenient: adjust weights — higher weight on critical monitors makes their failure impact the group score more