Syed Hashmi.
Work

Server monitoring

Othoni.

Server monitoring in one process and one file.

Status
Active
Live

Stack
  • Node.js
  • React
  • Express
  • SQLite
Licence
MIT
Last update
Oct 2026
Source
Source on GitHub
Othoni dashboard in dark mode. A left sidebar lists sections from Dashboard to Settings. The main panel shows a line chart of CPU and memory over the last hour, then four stat cards: CPU usage 14.0% on 4 cores with load averages, RAM 51.4% (3.9 of 7.6 GB), disk 29.1% (20.8 of 74.8 GB) and network throughput, each with a small sparkline. Below them is a per-core CPU heatmap with 15m, 1h, 6h and 24h range buttons.
The live dashboard: an hour of CPU and memory, current resource cards with sparklines, and a per-core load heatmap.

Live metrics, history, alerts and uptime, certificate, DNS and heartbeat checks — one Node process and one SQLite file, no agents, no chart libraries.

Why I built it

Most monitoring stacks want an agent, a time-series database and a charting server before they show you a single graph. I wanted to drop one thing on a server and have a dashboard.

What it does

  • Live system view — CPU per core, memory, disks, disk I/O, network, processes, Docker containers and systemd services.
  • History — 24 hours of metrics with zoomable charts and CSV export.
  • Alerts — threshold rules and checks that notify Discord, Slack, Teams, email, PagerDuty or Opsgenie.
  • Sentinel checks — website uptime, TLS certificate and domain expiry, DNS record changes, and heartbeats that catch cron jobs that stop running.
  • Fleet view — several servers on one dashboard through federation, plus a security audit with one-click fixes.

Engineering decisions

  • One process, one file — a single Node process and one SQLite file: no agents, no time-series database, no separate charting server.
  • Hand-written SVG charts — the history charts are drawn without a chart library.
Othoni's Sentinel page in dark mode. A green summary card says 'All 14 checks passing' and gives the soonest certificate expiry as 34 days. Filter chips sort checks into Websites, Certificates, DNS, Domains and Heartbeats. A card for syedhashmi.trade lists a website check at 36 ms with a latency sparkline, a TLS certificate with 89 days left and a pinned DNS-records check. Below it are a domain registration card (971 days left) and a heartbeat check waiting for its first ping.
Sentinel: uptime, TLS expiry, DNS drift, domain renewal and heartbeat checks, grouped by site.
Othoni's History page in dark mode, set to the 6-hour range and scrolled to the Per-core and Memory sections. A wide chart plots CPU use for each of four cores (c0 to c3) in separate colours over six hours. Below it, a memory-usage line chart sits next to a stacked area chart that splits memory into active, cached, buffers and free. Each chart has a CSV download button.
History: six hours of 5-second samples, including per-core CPU and a memory breakdown, each exportable as CSV.

Recent updates

  1. 0.79.0 — easy install: accounts, setup link, Docker
  2. 0.78.0 — Google-only sign-in
  3. 0.77.0 — “Set up alerts” card on Sentinel
  4. 0.76.0 — “Sentinel” checks page + certificate renewal