Open Status
Use the Status console

Use the Status console

Console navigation, organization scope, search, notifications, and help.

The Status console provides monitoring, incident response, maintenance, and status-page management for the active organization.

If this is your first visit, start by checking the organization and environment shown in the sidebar. Those two choices establish the context for almost everything else you see or change.

Screen layout

The console has three main areas:

  1. The sidebar moves between work areas and selects your organization and environment.
  2. The top bar shows your current location and provides health, search, appearance, notifications, help, and profile controls.
  3. The page workspace contains the lists, dashboards, forms, or editors for the selected work area.

Console dates and times use the timezone saved in your profile; maintenance windows use the organization's default timezone and display that timezone while you edit them.

Choose the correct scope

Status keeps organizations separate. An organization owns its monitors, incidents, maintenance windows, status pages, alert channels, agents, and operational resources. If you belong to more than one organization, use the organization switcher near the top of the sidebar. Switching organizations reloads the page in the new workspace; it does not copy or move a record.

The environment selector appears in the sidebar and in the top bar. Choose an environment such as production or staging to narrow supported console views, or choose All environments to remove that filter. Environments come from monitor classification. Changing this selector filters the workspace; it does not change a monitor's saved environment.

Before creating, editing, or deleting anything, use this quick check:

  • Is the organization name the one you expect?
  • Is the environment specific enough for the task?
  • Do the page title and filters match the records you intend to change?
  • Does your role allow the action?

If a list appears empty, select All environments and clear the page's search, status, tag, folder, and ownership filters before assuming data was removed.

Move through the sidebar

The sidebar groups pages by the kind of work they support.

Monitoring

  • Overview is your personal operational dashboard. Boards and widgets can summarize service health, incidents, maintenance, workers, alerts, on-call coverage, objectives, and other live information.
  • Monitors is the service-check inventory. Create checks, inspect health and results, run draft tests, pause or resume checks, and manage monitor metadata.
  • Incidents contains active, acknowledged, and resolved service disruptions. Select an incident to open its response workspace.
  • Maintenance plans expected service work and records its progress.

Response

  • Alerts configures notification destinations, routing, and pacing.
  • On-call manages schedules and coverage.
  • Escalation defines who is paged when a response is not acknowledged, and in what order.
  • Objectives tracks service-level objectives and error budgets.
  • Deployments records release events and their relationship to service health.
  • Operations toolkit collects reusable templates, rules, reports, API keys, and recoverable deleted records.

Visibility

  • Analytics explores availability and response-time history and exports reports.
  • Status pages builds the service-health pages shared with customers or other audiences.

Management

  • Agents shows the workers that perform monitoring checks and lets authorized users register private agents.
  • Setup health highlights deployment and configuration problems that can make monitoring or notification delivery incomplete.
  • Team manages members, invitations, roles, and teams.
  • Audit log records attributable administrative and operational changes.
  • Settings opens personal, organization, console, and—on self-hosted deployments—instance configuration.

Numbers beside a sidebar item are summaries, not a substitute for opening the page. For example, the monitor count follows the current environment, while an incident count calls attention to open response work.

Use the top bar

The breadcrumb confirms the page you are on. The remaining controls work from any console page:

  • The clock uses your profile timezone.
  • The health and environment control shows the selected environment's overall state. Open it to change environments or go to Public status pages.
  • Search opens the command palette. Use Command+K on macOS or Ctrl+K on Windows and Linux when the shortcut is available.
  • The theme control switches light and dark appearance quickly.
  • The bell opens your personal notification inbox.
  • Help and tours offers walkthroughs for the current page, longer guided journeys, the welcome tour, the command palette, and documentation.
  • Your profile picture opens your user profile. Settings in the sidebar opens the full account-settings window.

Status refreshes monitor, incident, and maintenance data automatically. Complete or cancel open forms before navigating away; unsaved text is not committed.

Find something or start an action

Open Search or press Command/Ctrl+K to use the command palette. You can type part of a page name, monitor name, or command instead of navigating through the sidebar. The palette can:

  • open any console page;
  • find among the first 40 monitors in its current monitor index;
  • start a new monitor, incident, maintenance window, or status page;
  • open account, appearance, or language settings;
  • switch the theme or sign out; and
  • start available page tours, detailed feature tours, and multi-page tours.

If a monitor does not appear in palette results, open Monitors and use the full list filters. The palette is a quick jump tool, not the complete monitor catalog.

Work with lists, drawers, and forms

Most work areas use the same interaction pattern: find a record in a list, select it for detail, then use a button or row action to make a permitted change. Search and filters affect what is visible; they do not delete records.

Creation and editing often happen in a drawer or modal window. Read the section labels, required-field markers, hints, and validation message before saving. For complex editors, such as monitors and status pages, work through each tab instead of assuming the first tab contains every important setting.

Use these habits for safer changes:

  1. Check scope and ownership before opening the form.
  2. Use a clear name that another responder will recognize under pressure.
  3. Keep secrets out of descriptions, incident discussion, public messages, and other ordinary text fields.
  4. Use Test configuration for a monitor draft before saving it when possible.
  5. Read the confirmation dialog carefully before a bulk action or deletion.
  6. Reopen the saved record and confirm its displayed state.

A missing or disabled action usually means your role does not allow it, the record belongs to another organization, or the record's current state makes the action invalid. See Roles, members, and teams for the permission model.

Read and manage notifications

Select the bell to open your inbox without leaving the current page. The inbox shows All, Unread, Open, Direct, and Archived views, supports search, and can load older items when more are available. Depending on the current view, you can open an item's related record, mark it read, dismiss it, restore it, or mark all unread items read.

The settings control in the inbox header opens Settings → Notifications. Those choices belong to you and control personal delivery categories and browser-push registration. They do not edit organization alert channels or their routing; use Alerts for those. The distinction is covered in Notification center.

Use help and tours

Open Help and tours when a page is unfamiliar. A page tour explains the main regions of that screen. A detailed tour focuses on a complex editor, and a tour follows a task across several pages. The welcome tour reintroduces the console shell.

Replay completed tours from the help menu. Reset seen tours clears tour completion state. Tours provide navigation guidance and do not modify records.

Change your settings

Open Settings and search or choose a section:

  • Profile changes the name, handle, picture, biography, password, and timezone associated with your account.
  • Notifications controls your personal delivery preferences and devices.
  • Organization changes workspace identity, retention, and default timezone when your role permits it.
  • Instance configures deployment-wide identity, mail, storage, proxy, and shared-worker settings on self-hosted deployments. It is hidden when cloud deployment policy manages those values.
  • Appearance controls theme, text size, density, corners, and accent.
  • Language changes console language and regional formatting for this device.
  • Security & sessions shows sign-in/session information and API keys.
  • Tags & folders maintains reusable monitor classification.
  • Workspace summarizes what the current console is watching.

Personal display choices do not alter another member's console. Organization and instance choices have a wider effect, so confirm your active organization and read the field hints before saving them.

Troubleshoot the console

When the page does not show what you expect:

  1. Confirm the organization and environment.
  2. Clear page filters and try the full list instead of command-palette results.
  3. Check whether your role permits the action.
  4. Read the complete on-screen error and correct the named field or conflict.
  5. Replay the current page tour if the control's location is unclear.
  6. Check Setup health if data is broadly stale, workers are missing, or notifications are not leaving the installation.
  7. Ask an administrator to inspect the Audit log when you need to know who changed a shared record.

Do not repeatedly submit a form after an unknown error. First confirm whether the record was created or changed; this avoids duplicate incidents, maintenance windows, or operational resources.