System Status & Telemetry
A live, single-page view of Moftgate host health: CPU, memory, disk, services, infrastructure, external dependencies and directory permissions.
What is the System Status page#
The System Status page gives you a real-time, single-page overview of the Moftgate host’s health. Every metric - CPU load, memory, disk, running services, database and cache telemetry, network traffic, external dependency latency, and directory permissions - is captured live the moment you open the page. There is no mock data, no synthetic sample, and no cached snapshot: what you see is what the host is reporting right now.
The page is organized into six clear sections, each rendered as a modular panel: overview cards, resource charts, services, infrastructure, external dependencies, and directory permissions.
- 1Open the General menu
In the sidebar, expand the General group to reveal the settings pages.
- 2Choose System Status & Telemetry
Select the System Status & Telemetry entry. The page opens as a full single-page overview of the host’s health.
- 3Read the live data
Every metric on the page is captured live from the host the moment you open it - there is no cached snapshot and no mock data.
Overview cards#
At the top of the page, four KPI stat cards give you an instant read on host pressure: CPU usage, memory usage, disk usage, and the total endpoint count. The first three shift color as they cross thresholds, so a glance is enough to spot trouble.
| Card | Threshold coloring |
|---|---|
| CPU % | Amber at 65% and above · Red at 85% and above |
| Memory % | Amber at 65% and above · Red at 85% and above |
| Disk % | Amber at 65% and above · Red at 85% and above |
| Endpoint count | Neutral slate - informational only |
Resource charts#
Below the cards, three charts sit side by side to give you a visual sense of resource usage. Each chart shows its metric exactly once - nothing is duplicated elsewhere on the page.
| Chart | What it shows |
|---|---|
| Memory doughnut | Shows used versus available memory as a ring. The colored arc is the portion in use; the muted remainder is free. |
| Disk doughnut | Shows used versus available disk space as a ring, in the same style as the memory doughnut. |
| CPU load bar chart | Plots the 1-minute, 5-minute, and 15-minute load averages side by side, with a reference line marking the host’s core count so you can see at a glance whether load exceeds capacity. |
Services#
The Services section lists everything that has to be running for the appliance to work, split across three columns. Status badges are deliberately neutral slate for online and red for offline - there is no green “healthy” badge, because the page is built to surface problems, not to celebrate normalcy.
| Column | What it lists |
|---|---|
| Core services | The backbone services the appliance depends on: PostgreSQL, Redis, the queue worker, and NATS. Each shows an online or offline badge. |
| PM2 processes | Application and Node.js processes managed by the process manager. Each process lists its name and current state. |
| Docker containers | Every container in the appliance stack. Each container shows its name and whether it is running or stopped. |
Infrastructure#
The Infrastructure section covers the deeper telemetry that keeps the appliance running: database and cache health, network traffic, and high-level system facts. Like the Services section, it is split into three columns.
| Column | What it shows |
|---|---|
| Database & cache | Shows the database driver, database size, active connections, queued jobs, number of cached keys, and how long the cache has been running. |
| Network I/O | Cumulative bytes received (RX) and transmitted (TX) across the host’s network interfaces since boot. |
| System | The runtime environment, host uptime, the number of registered users, and the total endpoint count. |
External dependencies#
This section measures how long the host takes to reach the upstream services it depends on. A full-width horizontal bar chart plots each dependency’s latency in milliseconds, with a status badge rendered below the chart for each one. Long bars mean slow responses; a red badge means a dependency is unreachable.
Directory permissions#
The final section checks that the framework can actually write to the paths it needs. Each path is tested for writability and shown as writable or not, so you can catch permission problems before they cause runtime errors.
| Path | Purpose |
|---|---|
| storage/ | Application storage - uploads and framework-generated files. |
| storage/logs/ | Application and framework log files. |
| storage/framework/cache/ | Framework cache data. |
| bootstrap/cache/ | Bootstrap and package manifest cache. |
Design principles#
The page follows a small set of deliberate design rules so the data stays the focus.
- Serious, muted palette - a slate base with a single accent. Color appears only for critical thresholds: red at 85% and above, amber at 65% and above. Nothing decorative competes with the data.
- No green badges - a service is either running (neutral slate) or down (red). The absence of a “healthy” color keeps your eye trained on what actually needs attention.
- No duplication - each metric appears exactly once. Memory lives only in the doughnut, disk only in the doughnut, CPU only in the bar chart, network only in Infrastructure, services only in the Services section, and external dependencies only in the latency chart.
- Dark mode - every component supports a dark variant, so the page reads cleanly in both light and dark panel themes.