simply-fxENGINE LENS
Connecting

SIMPLY-FX / INFRASTRUCTURE

The engine, in focus.

A clearer view of the systems behind your trades. Select a server, follow a metric, and inspect the details.

01 SERVER DB / moonbase
02 OBSERVATION WINDOW
03 METRIC

Engine telemetry

Waiting for the selected server.

Connecting
Latest readingWaiting for samples
Sample averageReturned window
Window peakReturned window
First → latestAbsolute change
Engine metric chart
Loading telemetry…
Waiting for samplesNo successful refresh yet

04 / THE BIGGER PICTURE

One fleet. A clear comparison.

Compare allocated resources. Select any server to inspect it above.

Waiting for metadata
No successful refresh yet
COMPARE BY
Server allocation comparison

Allocated capacity, not current utilization. Price is the reported server plan, not an invoice.

Server status comes from droplet metadata. “Active” does not verify the bot, database, website or mail service itself.

Understand the readings   Definitions, calculations and data limits

Load & processor activity

Load retains the 1-, 5- and 15-minute series. It is not a CPU percentage. Allocated vCPUs are shown for context; this page does not infer application health from them.

CPU percentages use changes in the API counters, divided by elapsed seconds and allocated vCPUs. Valid timestamps determine elapsed time; when that is unavailable, the original 120-second assumption is used and disclosed. Total uses 100 − idle when available, otherwise user + system.

Memory, disk & network

Memory used = total − available. Available, free and cached memory overlap; they are not additive. Disk used = size − free. Both are shown as percentages, as in the existing engine page.

Bandwidth preserves the existing API-to-Mbps interpretation. Outbound traffic is drawn below zero for separation, but its readout is positive. Units must match your backend contract; they are not inferred from response magnitudes.

Freshness & coverage

Refresh time is when this browser received data, not when the server sampled it. Latest-sample age is shown separately. Missing data stays unavailable; only readings returned by the live API are displayed.

Summary statistics use all valid returned primary-series samples, not just the drawn points. The average is an arithmetic sample mean, not a time-weighted mean. CSV includes the full returned series. Ambiguous timestamps are reconstructed and explicitly labelled; no uptime or service-health guarantee is implied.