Skip to content
Aloft Docs

Tags & organizing monitors

A handful of monitors fit on one screen. A hundred don’t. Tags plus the dashboard’s search and status filters keep a large fleet navigable — so you can pull up “everything on the payments team” or “every production monitor that’s down right now” in a couple of clicks.

Tagging a monitor

Section titled “Tagging a monitor”

Tags live on each monitor’s create and edit forms. Enter them as a comma- or newline-separated list. A few rules worth knowing:

  • Tags are lowercased and trimmed automatically, so Prod and prod become the same tag — you won’t end up with near-duplicates.
  • Each tag can be up to 40 characters, and a monitor can carry up to 20 tags.
  • The set of tags is shared across your whole organization, so a tag you add on one monitor immediately becomes available as a filter for all of them.

Filtering the dashboard

Section titled “Filtering the dashboard”

The dashboard has a filter bar with three independent controls. They combine, so you can narrow on all three at once.

  1. Search — type into the “Search by name or URL…” box and press Search. It matches against the monitor’s name and its target URL, so a fragment like api or checkout finds everything related.
  2. Status chips — a row of chips: All, Up, Down, Degraded, Paused, and Pending. Click one to show only monitors in that state. (Pending is the chip for brand-new monitors that haven’t finished their first check.)
  3. Tag chips — one chip per tag in use across your org, plus an All chip. Click a tag to show only monitors carrying it. This row only appears once you’ve actually tagged something.

A Clear button resets search, status, and tag in one click whenever any filter is active.

Tagging conventions that scale

Section titled “Tagging conventions that scale”

Tags are free-form, but a little consistency goes a long way. A practical approach is to give each monitor a tag from a few fixed dimensions:

  • Environment — prod, staging, dev. Almost always the most useful first filter.
  • Team or owner — payments, platform, growth. So the right people can pull up exactly what they’re responsible for.
  • Criticality — tier-1, tier-2, or critical vs. best-effort. Lets you separate “wake someone up” monitors from the nice-to-haves.

You might also tag by service (checkout, auth, cdn) or by region for multi-region deployments. Pick a small vocabulary, write it down somewhere your team can see it, and apply it consistently — the value of tags comes entirely from everyone using the same words.

Section titled “Related”