Critical alerts open· updated

Settings

Read-only snapshot · edit via .env on .187 /opt/monitoring and restart monitoring-web / monitoring-worker.

Runtime

NODE_ENVproduction

DatabasePostgres · •••••••••••••••••••••••••

Last server SSH cycle7/11/2026, 2:15:13 AM

Last alert created7/9/2026, 10:00:03 PM

Schedules

Server SSH cadence15 min

Endpoint HTTP cadence15 min

HTTP timeout10000 ms

Alert thresholds (worker-side)

CPU warn / crit80% / 95%

Memory warn / crit80% / 92%

Disk warn / crit80% / 92%

Endpoint latency warn / crit2000 ms / 5000 ms (hard-coded)

Cert expiry warn / crit≤30d / ≤7d (computed in /certificates)

Integrations

Telegram bot token

86620759••••••••••••••••••••••••••••••••••••••

Telegram chat id5453763927

Dashboard bearer (POST /api/register, /api/metrics)

3778fa••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Inventory

Active servers3

Projects (all status)8

Enabled endpoints8

ProjectMetric rows total0

🔒 Auth: dashboard is currently read-only / unauthenticated. POST routes (/api/register, /api/metrics, /api/alerts) require the Bearer token above. Login UI is intentionally not wired.