⚡ SysMonitor

📖 1. What is SysMonitor?

SysMonitor is a lightweight, self-hosted power & network outage monitoring tool built specifically for COX's Bazar CLS (COXCLS), a facility operated by BSCPLC that relies on grid power (PDB) with a generator + Automatic Transfer Switch (ATS) as backup.

It runs entirely on the local network and works passively — it only observes network reachability of monitoring points already on site. It does not connect to, control, or issue commands to the generator, ATS, or any power infrastructure. Its only job is to watch, record, and alert.

The idea is simple: instead of someone on shift having to notice a power drop, write it down on paper, and remember to log when the generator kicked in, SysMonitor watches two always-on network devices and infers the facility's power state from their reachability — then keeps a permanent, timestamped record of everything that happened, without anyone needing to touch a keyboard.

⚙️ 2. How it works

SysMonitor is a Django web application paired with a lightweight background monitor process. The two run as separate, independent services and communicate only through the shared database — so a restart of one never takes down the other:

🏗️ 3. Architecture

SysMonitor is deliberately split into small, independent pieces, each run as its own systemd service so a crash or restart in one never brings down the rest of the system:

Three independent services, one shared database — that's the whole system:

🧠 4. The detection logic

A full, healthy outage cycle looks like this — grid drops, generator picks up the load, grid comes back, and the ATS quietly switches the load back to grid power:

Every completed cycle is classified so abnormal situations stand out instead of getting lost in the log:

Why two devices instead of one?

Relying on a single ping target is unreliable — a device rebooting, a single WiFi hiccup, or a switch port flapping can all look identical to a real power outage. By requiring both the Holder and the NVR to agree before a state change is confirmed, one-off blips are filtered out automatically, and only genuine power events reach the log and the notification channels.

A maintenance mode can be switched on before planned network work (e.g. restarting a router), which pauses outage detection and notifications so planned downtime never gets logged as a false power outage.

✨ 5. Features

🧩 6. Tech stack

Built to be simple to operate on a single on-site machine — no external cloud dependency for the core monitoring loop:

📢 7. Notifications

SysMonitor can alert designated recipients the moment a power event happens, over multiple channels:

What triggers an alert

• Outage start — sent once, the moment the Holder device goes down.
• Critical — sent once if both reference devices are unreachable for an extended period.
• Alarm — sent once per cycle if the generator or ATS doesn't behave as expected.
• Cycle complete — sent once the cycle closes cleanly (power restored, ATS switched back).

Each of these fires at most once per cycle — the dispatcher keeps track of what's already been sent, so recipients never get spammed with duplicate alerts for the same event.

📱 8. Android App

A lightweight Android wrapper app is available for quick access to the SysMonitor dashboard from a phone — it automatically detects whether you're on the facility's local network or an external connection and loads the right address for you.

🔐 9. Roles & Access Control

Access to the dashboard is account-based. Every account is assigned a role that determines exactly which pages appear in its navigation:

When a user updates a sensitive field on their own profile (like their email or mobile number), the change is held as pending until an admin reviews and approves or rejects it — this page and its approval controls live right inside the admin's Users tab, so nothing changes silently.

This About & Docs page itself is the one exception to account-based access — it's intentionally public so anyone can understand what SysMonitor does before ever needing an account.

❓ 10. FAQ

👤 11. About Us

SysMonitor is built and maintained in-house for the COXCLS NOC team at BSCPLC, to reduce manual outage tracking and give the team real-time visibility into facility power health.