K Kituwa Automations
--:--
SM

Infrastructure · Systemd timer

Service Monitor

Collects the server's service-monitor metrics every minute for the Kituwa Hub.

Healthy Every 60 seconds

Control panel

Run it now or change the timing.

Read-only view. Unlock the controls to run jobs, post now, or change schedules.

Actions

Service Monitor controls

Change the timer

Writes a systemd drop-in, validates it, reloads systemd, and restarts the timer.

Timing

Timer and service state.

The control panel above can run this job now or rewrite its timer.

Systemd

kituwa-monitor.service

Active state
inactive / dead
Result
success
Exit status
0
Started
Thu Nov 19, 11:18 AM
Finished
Thu Nov 19, 11:18 AM
Timer
kituwa-monitor.timer
Timer expression
—
Next run
Thu Nov 19, 11:23 AM in 3m
Restarts
0

Logs

Latest output

{
  "checked_at": "2026-11-19T16:18:06+00:00",
  "counts": {
    "down": 3,
    "ok": 133,
    "paused": 22,
    "unknown": 3,
    "warn": 2
  },
  "duration_ms": 20369,
  "errors": [],
  "ok": true,
  "open_incidents": 3,
  "services": 163
}
kituwa-monitor.service: Deactivated successfully.
Finished kituwa-monitor.service - Kituwa service monitor collection.
kituwa-monitor.service: Consumed 2.572s CPU time over 20.878s wall clock time, 57.4M memory peak.

Paths and runbook

Where it lives, how to run it.

Token values are never rendered. Copy paths and commands directly from here.

Paths

Files and services

Working Directory /home/ubuntu/opencode/runchero/kituwa-hub
Config /home/ubuntu/opencode/runchero/kituwa-hub/.env
Logs journalctl -u kituwa-monitor

Runbook

Commands

Run now
sudo systemctl start kituwa-monitor.service
Logs
journalctl -u kituwa-monitor -n 50