Server overview
A server's first tab: the identity details, what the four live gauges actually measure, and the menu down the side.
Opening a server from the services list lands you on the Overview. It carries the power controls, four live gauges, the charts underneath them, and the cards that describe the machine and its billing.
A server that has never been built, or that is building right now, does not show this page at all. It shows the setup or build screen instead, covered in While your server builds.
Identity
The heading is the server's name. Under it sit a status badge, a region chip with the city and a short region code, a chip carrying the label the service is stored under, and the next renewal date. That label chip is not the machine's own hostname, which is reported separately in the System card. The region shown is the customer-facing location, never the internal node the machine runs on.
The System card in the left column holds the rest:
| Row | What it is |
|---|---|
| Operating system | The image currently installed |
| Virtualization | The virtualization type of the machine |
| Hostname | Reported by the agent inside the VM. Reads Not yet reported by guest until it is |
| Location | City and region code |
| UUID or Server ID | The machine's identifier. It reads Server ID when no UUID has been reported |
| Built | When the current install was created |
The menu down the side repeats the name with the live power state under it: Running, Starting, Stopped, Paused, or Suspended.
The live gauges
Four rings sit under the power controls.
| Gauge | What it measures | Where the number comes from |
|---|---|---|
| CPU usage | Percent of the server's cores in use, with the vCPU count beneath | The hypervisor's live state, and only while the server is running |
| Memory | Used against total, calculated the way free does: total minus free, buffers, cache, and reclaimable slab, so it matches what you see inside the VM | The agent inside the VM |
| Storage | Used against total on the root filesystem | The agent inside the VM |
| Bandwidth | This period's traffic against your plan's cap | Monthly traffic counters |
The page renders once on load, then refreshes every 15 seconds. Refreshing pauses while the browser tab is in the background and picks up again when you return to it. The underlying reading is cached for 15 seconds on our side, so several views of the same server share one fetch rather than each forcing a new round trip. A small live chip flashes in the corner on every successful refresh.
CPU, Memory, and Storage all depend on the qemu-guest-agent running inside your VM. Without it, Storage shows a dash instead of a percentage and Memory falls back to the figure your plan allocates, with Allocated written under it. A ring reading 0% with Allocated beneath it means the server is not reporting, not that nothing is in use. Bandwidth does not depend on the guest agent.
A failed refresh is silent. The gauges keep showing the last good numbers with no error, so figures that have stopped moving and a missing live chip mean the panel is not getting fresh data. Reload the page before believing an unusual reading.
The rings in the side menu
Three compact rings, CPU, MEM, and DISK, sit at the bottom of the per-server menu on every tab. Same source, same 15 second refresh. They show a placeholder while loading and a dash when a value is not available, and they disappear entirely when you collapse the menu to icons.
CPU only reads while the server is running. MEM and DISK do not check the power state, so on a stopped server they keep showing whatever came back last.
The charts underneath
Below the cards, the same four measurements are drawn over time: CPU, Memory, Disk, and In · RX / Out · TX. The range chips are 30m, 1hr, 12hrs, 1d, and 1wk, bucketed at 1 minute, 2 minutes, 10 minutes, 30 minutes, and 2 hours respectively. They refresh every 30 seconds.
This history is Clouduxe's own recording, not an archive kept by the hypervisor. Points are stored when something was collecting, which means a period nobody was watching has no data, renders as a gap in the line, and never fills in afterwards. Recorded points are kept for 30 days.
The rest of the cards
- Network usage: inbound against outbound across recent billing periods, with Inbound (this period), Outbound (this period), and Total / cap. The cap reads Unmetered when your plan reports none.
- Resources allocated: vCPU cores, Memory, Storage, and Bandwidth, as sold to you. Read the gauges for what is in use.
- Lifecycle: Billing cycle, Renews, Recurring price, and on an active service the Auto-renew switch and Renew early. See Renewal and cancellation.
- Quick connect: Assigned IPv4 with a copy button, then either the SSH command for that address or, on Windows, Remote Desktop with a Download .rdp button. See Connecting to your server.
- Clouduxe Prism: a protection summary with an Open firewall link. When protection is not set up for that server the card reads Coming soon.
- Cancel service sits at the bottom of the right column. What cancellation does, and when it takes effect, is covered in Renewal and cancellation.
The power bar across the top is covered in Power controls.
DDoS protection in Resources allocated reads Always-on, and so does Mitigation in the Clouduxe Prism card. Both are fixed text. They read the same whether or not protection has been provisioned for that particular server, so neither one tells you anything about this machine. The Firewall tab is where the real state lives: whether protection is active or paused, which ports carry rules, and which sources are blocked. Check there before assuming a server is filtered. See The Firewall tab.
The per-server menu
The sidebar swaps to a per-server menu while you are inside a service, with All servers at the top to get back out. On a narrow screen the same items become a tab strip above the content.
| Group | Item | What it covers |
|---|---|---|
| Manage | Overview | This page |
| Manage | Options | Reinstalling, resetting the root password, and read-only boot settings |
| Manage | Console | Console access |
| Manage | Network | Networking and IPs |
| Manage | Storage | Extra storage |
| Manage | Backups | Backups |
| Manage | SSH Keys | SSH keys |
| Clouduxe Prism | Firewall | The Firewall tab |
| Clouduxe Prism | Attacks | Reading the Attacks tab |
| Clouduxe Prism | Event log | Recent drops at the edge, capped at the latest 50, from a 1-in-64 sample rather than every packet |
| System | Logs | Activity and logs |
Two things change what you see there:
- Console, Network, Storage, Backups, and SSH Keys only appear when there is a machine behind the service. A DDoS-Protected Proxy has no VM of its own, so it gets a shorter menu, and its Overview carries only the protection and lifecycle cards.
- Attacks and Event log only appear when attack analytics is switched on. Firewall is always there.