Groups

Groups are logical containers that organize your monitors. Every monitor belongs to exactly one group, and each group automatically gets its own status page.

How Groups Work

Groups provide a way to logically separate your monitors based on how your infrastructure is organized. How you use them is entirely up to you — here are some common patterns:

By client (multi-tenant): If your infrastructure serves multiple clients with separate instances, create a group for each client. Each client gets their own status page showing only their monitors.

├── Acme Corp          → status page: /status/acme-corp
│   ├── API Server
│   ├── Dashboard
│   └── Database
├── Globex Inc         → status page: /status/globex-inc
│   ├── API Server
│   └── Dashboard

By environment: Separate production from staging to keep your monitoring organized and your status pages clean.

├── Production         → status page: /status/production
│   ├── API
│   ├── Website
│   └── Workers
├── Staging            → status page: /status/staging
│   ├── API
│   └── Website

By service category: Group monitors by the type of service they represent.

├── Core Services      → status page: /status/core-services
│   ├── Authentication API
│   ├── Payment Gateway
│   └── Database
├── External APIs      → status page: /status/external-apis
│   ├── Email Provider
│   └── CDN

Default group: If you don’t need any of the above, just use the Default group that ships with Warden. It works perfectly for simple setups.

Groups and Status Pages

Every group automatically creates a status page. This is by design — it saves you from having to manually create and link status pages every time you add a group.

When you create a group called “Production”, a status page is immediately available at /status/production showing only the monitors in that group.

In addition to per-group pages, Warden provides an All status page that displays monitors from every group in a single view.

Status Page States

Auto-created status pages start as disabled by default. This means they exist but return a 404 until you enable them. This lets you set up your groups and monitors first, then enable the status pages when you’re ready.

To enable a status page:

1. Navigate to Settings → Status Pages
2. Find the page for your group
3. Toggle Enabled on
4. Save

Public vs Private

Each status page can be either:

• Public — anyone with the URL can view it, no login required. Use this for customer-facing status pages.
• Private — requires authentication to view. Use this for internal teams or when you want to control who sees the page.

Restricted Access with Status Viewer

For scenarios where you need to give someone access to a specific status page without giving them dashboard access — for example, sharing a client’s status page with that client — use the Status Viewer role.

1. Create a user with the Status Viewer role in Settings → Users
2. Assign one or more status pages to that user
3. Share the credentials — they’ll see only their assigned pages after logging in

This is especially useful in multi-tenant setups where each client should only see their own group’s status page.

See User Management for details on managing Status Viewer assignments.

Default Group

Warden ships with a Default group that cannot be deleted. If you don’t need multiple groups, add all your monitors here.

Creating a Group

1. Click the + button next to “Groups” in the sidebar, or navigate to the dashboard and click New Group
2. Enter a name (max 255 characters)
3. Click Create

The group appears immediately in the sidebar with a corresponding status page auto-created in Settings.

Groups are sorted alphabetically (case-insensitive) in the sidebar and dashboard.

Renaming a Group

1. Find the group in the sidebar
2. Open the dropdown menu and select Edit Group
3. Enter the new name
4. Save

The group’s internal ID does not change when renamed.

Deleting a Group

1. Find the group in the sidebar
2. Open the dropdown menu and select Delete Group
3. Confirm the deletion

Caution

Deleting a group permanently deletes all monitors in that group, along with their check history, events, outage records, and the associated status page. This cannot be undone.

The Default group cannot be deleted.

Group Status

Each group shows an aggregated status on the dashboard overview:

Status	Meaning
Operational	All monitors in the group are up
Degraded	One or more monitors have high latency
Unavailable	One or more monitors are down
Maintenance	A maintenance window is active for this group

The worst status takes priority — if any monitor is down, the group shows as Unavailable regardless of other monitors’ states.

Groups and Maintenance

Maintenance windows are associated with groups. When a maintenance window is active for a group:

• All monitors in the group continue running checks
• Notifications are suppressed for the duration
• The group shows a “Maintenance” status on the dashboard and status pages

Groups and Incidents

Incidents can affect one or more groups. When creating an incident, you select which groups are affected. This determines:

• Which monitors show as impacted on status pages
• Which groups display incident banners on the dashboard

Permissions

• Admin and Editor roles can create, rename, and delete groups
• Viewer role can see groups and their monitors but cannot modify them
• Status Viewer role cannot access the dashboard — they only see groups through assigned status pages