Groups Overview
Organize your monitored services into logical collections for faster triage and a cleaner dashboard.
Groups Overview
A group is a named collection of services and components that you create to organize your PulsAPI dashboard. Instead of scrolling through a flat list of every service you monitor, groups let you cluster related services together so you can assess health at a glance.
Why use groups?
| Use case | Example group |
|---|---|
| By team | "Backend Team" containing AWS, PostgreSQL, Redis, Datadog |
| By environment | "Production" vs. "Staging" with the same services split by role |
| By project | "Checkout Service" with Stripe, Cloudflare, GitHub Actions |
| By criticality | "Tier-1" for revenue-critical dependencies, "Tier-2" for everything else |
Groups appear as cards on your dashboard board. Each card shows the aggregated status of every service inside the group — if any member is degraded or experiencing an outage, the group card reflects that immediately.
How groups appear on the board
When you open your dashboard you will see each group displayed as a separate card. The card shows:
- Group name — the label you chose when creating the group.
- Service count — how many services and components are inside.
- Aggregated status — a single indicator (Operational, Degraded, Partial Outage, Major Outage) rolled up from the individual service statuses.
- Expand/collapse — click the card to reveal the full list of services with their individual statuses.
Services can belong to more than one group. Adding a service to "Production" does not remove it from "Backend Team".
What you can do with groups
- Create a new group and give it a descriptive name.
- Add services individually or in batch.
- Reorder groups on your board with drag-and-drop.
- Share a group with teammates or generate a public token link.
- Edit or delete groups at any time.
Continue to the next pages to learn how to create and manage groups and share them with your team.