Open Status
Monitor taxonomy and ownership

Monitor taxonomy and ownership

Classify monitors with tags, folders, environments, and ownership.

Status combines reusable taxonomy with per-monitor ownership metadata. Use the monitor editor to classify one monitor, bulk actions to replace classification across a selection, and Settings → Tags & folders to manage the shared tag and folder catalog.

Tags, folders, and environments

A monitor can have up to 20 unique tags, one folder, and one environment. Tags are short many-to-many labels (each up to 40 characters). A folder is the primary operational grouping; environment is a free text deployment boundary such as production or staging. The monitor list combines these with state and text filters, while the sidebar environment selector scopes supported console views.

Tags and folders also participate in automatic severity rules. Matching folder and environment can form an automatic incident grouping key, so classification changes can alter the shape of the next incident without changing current health.

Manage the catalog

The Tags & folders settings section creates, renames, recolors, and deletes tags and folders; folders also have a selectable icon. Usage counts show references from monitors and incident severity rules. Renaming a tag or folder updates its references. Deleting one removes the value from them, so review the displayed usage before confirming. Changes are organization-scoped and audited.

Environment values do not have a separate catalog: they are normalized from monitor configuration and appear in selectors when used.

Operational ownership

Every monitor can also carry a description, Tier 1–4 importance, planned/ active/deprecated/retired lifecycle, owning team, and runbook, repository, and dashboard links. These fields put triage context on the monitor, drive ownership views and notification targeting, and remain intact through clone, template, import/export, history restore, and reassignment where allowed.

An owning team is not an access-control boundary. Organization membership and roles still determine who can view or change a monitor; see Roles, members, and teams.