Organization

Good organization keeps monitor lists, status pages, maintenance windows, notifications, and incident review manageable as your monitor count grows.

Folders and Groups

Every monitor belongs to a folder and group. Folders can be nested, so use them for broad areas such as product, environment, or business unit. Use groups for services or workflows within those folders. Group detail pages can show both the monitors and reusable scenarios stored in that group.

/
  App Site
    Website Login
    API Health
  Marketing Site
    Homepage
    Pricing
  Services Clusters
    Admin Service
    Gateway
    Workers

Organization Monitor Settings

Organization settings define defaults used by new monitors:

Default region.
Default success criteria, including criteria by monitor type and custom scenario type.
Default metrics to capture and show.
Default notifications, including comment, check success, SSL expiry, and domain expiry settings.
AI-related settings for AI Conversations, MCP-connected agents, and AI scenario support when enabled.

Association Strategy

Status pages and maintenance windows can associate by monitor, group, folder, or tag. Prefer broad associations when the relationship is stable:

Use folders for all monitors in an area.
Use groups for a single service or workflow.
Use tags for cross-cutting events such as production or customer-facing.
Use direct monitor associations for exceptions.

Saved Monitor-List Layout

The monitor list can be grouped by folder/group, region, scenario, or combinations of those fields. Members with write access can save the current search query, state filter, sorting, grouping, and map visibility as the organization default.

Naming Best Practices

Name monitors after what users or systems experience, not only the implementation detail.
Include geography only when the monitor is region-specific.
Keep folder and group names stable because they are used in navigation and associations.
Use descriptions for details that would make names too long.