Public Control Plane

Readable backup oversight without exposing the private engine.

This dashboard combines private status snapshots with pushed private events, then turns them into a fast, web-friendly overview for your public VPS.

Healthy 1
Failing 2
Database 2
Mikrotik 1

Fleet

Private fleet node health

0 nodes are waiting for first verified data.

Node Type Host Status Last backup Artifact
db-myperwira
backup database failed: ssh dial 10.30.0.4:22: dial tcp 10.30.0.4:22: i/o timeout
 database 10.30.0.4 Error -
.
-
db-myperwiracloud
backup database failed: ssh dial 10.30.0.4:2222: dial tcp 10.30.0.4:2222: i/o timeout
 database 10.30.0.4 Error -
.
-
mikrotik-core-cyber
backup mikrotik completed: file=/var/lib/backup-mikrotik/storage/mikrotik/mikrotik-core-cyber-2026-03-28.rsc size=20.6 KiB duration=2.386s
 mikrotik 103.195.65.3 Healthy 28 Mar 2026 12:03
mikrotik-core-cyber-2026-03-28.rsc
20.6 KiB

Storage

Capacity signals

Database

0 files

-
Mikrotik

1 files

20.6 KiB

Activity

Recent events

db-myperwira ERROR

backup database failed: ssh dial 10.30.0.4:22: dial tcp 10.30.0.4:22: i/o timeout

28 Mar 2026 12:03
db-myperwiracloud ERROR

backup database failed: ssh dial 10.30.0.4:2222: dial tcp 10.30.0.4:2222: i/o timeout

28 Mar 2026 12:03
mikrotik-core-cyber OK

backup mikrotik completed: file=/var/lib/backup-mikrotik/storage/mikrotik/mikrotik-core-cyber-2026-03-28.rsc size=20.6 KiB duration=2.386s

28 Mar 2026 12:03
db-lab-1 INFO

success_without_open_incident: backup database completed

28 Mar 2026 10:05
db-myperwira INFO

incident_resolved: backup database completed

28 Mar 2026 10:05
db-myperwira ERROR

incident_opened: backup database failed

28 Mar 2026 10:00
db-myperwira ERROR

incident_updated: backup database failed

28 Mar 2026 10:00