Server overview

Click a server anywhere in MZPanel and you drop into its server-detail view (/servers/:id) — the workspace for one box. This page is an orientation: it explains the three-column shell, the grouped section menu, and the live info rail, so the per-section pages that follow feel like home. Available on all plans.

There’s no separate “Overview” tab

Opening a server lands you on Sites — the box’s home. There is no standalone overview dashboard; live health and hardware facts live in the right-hand Server info rail, which stays on screen no matter which section you’re in.

The three-column shell

On a wide screen the server view is three columns that frame one active section:

1. Left — the section menu. A grouped rail (see below) that swaps the center pane without a page reload. The active section is highlighted; the menu and info rail stay mounted as you move around.
2. Center — the active section. Sites, PHP, Cron, Monitoring, and so on render here. Only this column scrolls and reloads; the frame around it is stable.
3. Right — the Server info rail. A live panel of the box’s vitals: CPU / RAM / Disk / Swap gauges, Identity (IPv4/IPv6, hostname, OS, arch, kernel, timezone), Hardware (CPU model, frequency, virtualization), Activity (network, processes, load average) and Agent (agent version, uptime, registered date). It updates live over the same metrics stream the Monitoring page uses, and can be collapsed to a thin strip for more width.

The layout reflows on smaller screens: on a tablet the info rail is dropped (its key facts also appear in section headers), and on a phone the section menu becomes a horizontal scrolling strip on top with a server switcher and a sections dropdown.

The section menu, group by group

The rail is organised so the everyday sections lead and the deeper system tooling tucks away. The primary group has no header; System is collapsible and starts collapsed (it opens automatically when you’re in one of its sections). Item badges show live counts (sites, databases, PHP versions, certificates, cron jobs, users, extensions) read straight from the box.

• Main — Sites, Apps (Docker containers & stacks) and Databases.
• Web — PHP, DNS & TLS, Mail and Cron Jobs.
• Tools — Users & SFTP and File Manager.
• System (collapsible) — Services, Monitoring, Storage, OS Updates, Security and Extensions.
• Settings — Settings: server identity, facts and the danger zone.

Your role shapes the menu

On a shared team, the menu only shows what your role can use. An owner or admin sees everything; a developer loses the System and Tools groups; a client sees just Sites and Monitoring. If a section is missing, it’s a permissions boundary, not a bug — see Team roles.

How it works

The shell fetches the server record, live metrics and the section counts once, then shares them with every section through a common context — so switching sections never re-loads the frame. It drives a few pieces of real data:

• Vitals & gauges come from a per-box metrics snapshot the control plane polls while you’re watching and fans out over a live stream, so the info rail and the Monitoring page always show the same numbers with one poll per box (not one per viewer).
• Sites and Apps counts come from a live server.status job (mz status); the other badge counts (databases, PHP, certificates, cron, users, extensions) come from the agent-pushed inventory cache — instant, and still present when the box is offline.
• Identity & hardware facts come from a server.facts job (mz facts), cached on the control plane so an offline box still shows its last-known IP, CPU model and timezone rather than a blank.
• Online / offline & last-seen track a live heartbeat stream; the footer counts up “last seen” every second.

CLI & automation

The server view is navigation over the same engine the on-box mz CLI drives — there is no single “overview” command, but two read-only calls back the vitals you see here, and an on-box AI (ClaudeCode) reads them the same way:

mz --help                 # every command group available on the box
mz status --json          # sites/apps counts, service health, versions
mz facts --json           # identity + hardware facts (IP, CPU, virt, timezone)

Each section has its own richer commands — start from any per-section page, or see The mz CLI and the command catalog.

Gotchas & troubleshooting

• Sites is the home, not an overview. /servers/:id redirects to /servers/:id/sites; old /servers/:id/overview and per-server terminal links redirect to their new homes, so bookmarks still land.
• Offline shows the last-known state, not mock data. With the agent offline, the info rail and badge counts render from cache (dimmed / “last seen” in the footer); anything that needs a live read waits until the box reconnects.
• A gauge or fact that reads ”—” is loading, not broken. Each row resolves independently; a slow facts read leaves a placeholder rather than blocking the panel.
• Merged sections. Daemons is now a tab inside Services, and Logs a tab inside Monitoring — the old standalone menu rows are gone (deep-links redirect).
• The right rail hides when a drawer is open. Opening the AI chat or a docked detail panel takes the info rail’s place so panels don’t stack; close it to bring the rail back.

Related

• Connect a server — install the agent and register a box.
• Monitor a server — services, metrics, OS updates and storage.
• The mz CLI — driving the box from the command line.