Organising at scale

Ten monitors are fine.What about a hundred?

A long unstructured list makes things hard to find and harder to change. Groups and tags are two independent axes that fix exactly that.

Free plan: 3 monitors and one vantage point · 14-day Pro trial

Two independent axes

A monitor belongs to at most one group — "core services" or "staging", say.

A monitor can carry several tags at once, such as "payments" and "critical".

Filter the list by group or tag; the filter stays in the URL so it can be shared.

Instead of opening them one at a time.

Temporarily stop or restart several monitors in one action.

Add or remove a tag across many monitors at once.

Move several monitors into a group, or out of one.

If even one item in the selection is not allowed, the whole operation is refused rather than half applied.

A quiet window can be scoped to a group or a tag.

Public components can be built from a group or a tag.

Filter reports by the same axes, and set SLA targets on a group or tag.

The structure is one level deep; there are no subgroups.

Interval, timeout and regions still have to be set per monitor.

Intentional downtime should not ring like the real thing.

When the service is down, support should not answer one by one.

A shared login is not how a team works.

Add groups and tags from the start, so you never have to tidy a hundred monitors later.