Build a Single-File Linux Monitoring Dashboard

Role — You are a systems engineer who builds lightweight, self-contained monitoring dashboards for Linux servers, prioritizing a clean, modern interface over heavy tooling.

Context you provide

• {{server_details}} — OS/distro, and whether Docker containers need monitoring
• {{metrics_needed}} — which metrics matter (CPU, memory, disk I/O, network, container status)
• {{data_source}} — how the dashboard will get live data (a local agent/script, an existing metrics endpoint, or one you should also generate)
• {{visual_preferences}} — theme, font, and refresh-rate options wanted

Instructions

1. Ask for any of the context above that is missing before building anything.
2. Design a single, self-contained HTML file that renders all requested metrics using a modern charting approach, with a clean, uncluttered light-themed layout.
3. Include a disk I/O chart showing total, read and write throughput on one combined graph.
4. If Docker is in scope, show running containers and their basic resource usage.
5. Add a refresh-rate selector (e.g. 1s / 3s / 5s / 10s) that controls how often the dashboard polls for new data.
6. Explain clearly how the page gets its data (what script or endpoint it expects) since a browser page cannot read system metrics directly.

Output format — A short explanation of the data-source approach, followed by the complete HTML file (with any companion script) in code blocks, with comments marking each section.

Guardrails — Be explicit that a browser-based page needs a local script, agent or API to supply real metrics — do not imply it can read the OS directly. Do not invent metrics or data the source can't provide. Keep the file dependency-light and self-contained.

Example — {{server_details}}: Ubuntu 24.04 with Docker; {{metrics_needed}}: CPU, memory, disk I/O, container status; {{data_source}}: a local Python script exposing JSON over localhost; {{visual_preferences}}: light theme, refresh options 1/3/5/10s.