← Back to Reliability

CustomerNode Watchdog — Nightly Health Report (sample). Synthetic data; not a live production report.

SYNTHESIZED SAMPLE. This is the production CustomerNode Watchdog report, rendered from the real template with synthetic data — real production values are not shown, and sensitive operational details are redacted.
CustomerNode
WATCHDOG
PRODUCTION
Good night, Operations
95
green
Key actions (1)
reboot_requiredKernel security update applied — reboot pending WARNING
At a glance
Security
Strong
No active threats
Resources
Healthy
Data volume 38%, root 40%, CPU peak 28%
Application
Healthy
12 errors across 128,400 requests today
Services & dependencies
Healthy
Services, infra, backups and external APIs all clean
Top risks (next 30–60 days)
No elevated risks — leading indicators are healthy.
Trends (last 24h)
Health score (24h) 100/100
uptime 100.0% · range 99–101 (↓1)
CPU load (24h) 21%
Memory (24h) 46%
Root disk · OS + Docker (24h) 40%
Data volume · DB + media + backups (24h) 38%
Trends (last 7 days)
Health score (7d) 100/100
uptime 100.0% · range 98–101 (flat)
CPU load (7d) 21%
Memory (7d) 46%
Root disk · OS + Docker (7d) 40%
Data volume · DB + media + backups (7d) 38%
Trends (last 30 days)
Health score (30d) 100/100
uptime 100.0% · range 95–101 (↑3)
CPU load (30d) 21%
Memory (30d) 46%
Root disk · OS + Docker (30d) 40%
Data volume · DB + media + backups (30d) 38%
Capacity
Root disk (OS + Docker)40.5% used
Data volume (DB + media + backups)38.5% used · ~888d of growth headroom to 80%
CPU peak (24h)28%
Memory peak (24h)51%
Services
All services8/8 healthy
Infrastructure
Backup freshnesscompleted 4h ago
Backup integrityverified — 2.3 GB archive
SSL certificatevalid — 68 days remaining
Security posture
STRONG
12 controls monitored · 2 SSH logins from 2 source(s) (7d) · 2 security events (24h) · 0 active threat(s)
SSH access log (last 7 days)
When (UTC)Source IPUser
May 31 16:10203.0.113.10deploy
May 29 18:10198.51.100.42deploy
Threats observed
  Failed-login / brute-force sources (7d)0
SECURITY  Web-probe scanners (7d)14
  Unexpected listening ports (7d)0
  Unexpected host egress (7d)0
  File-integrity changes (7d)0
Security controls
Integrity monitoring
  SSH authorized_keys unchangedunchanged
  Critical system files (FIM)no changes
Host & container hardening
  No unrecognized containersnone
  No privileged containersnone
  Docker socket access restrictednone
  Images from trusted registriesall from trusted registries
  No unexpected listening portsexpected set only
  No unexpected host egressexpected set only
Edge & application
  Cloudflare edge enforcededge enforced
  No web-probe scanningno anomalies this cycle
  API auth-abuse normalnormal
Patch & maintenance
WARNING  No pending OS rebootKernel security update applied — reboot pending
Application
Signups (yesterday)37
Active users (yesterday)1240
Requests (today, partial)128400
Errors (today, partial)12
Avg response time180
Slow requests (>1000ms)23
Slowest requests (24h)
GET /app/journey/detail
p95 1820ms · max 1820ms · 1 slow · db 62%, openai 23%, app 15%
POST /api/templates/import
p95 1240ms · max 1240ms · 1 slow · db 44%, app 32%, openai 24%
Worst single request
2026-06-01T22:10:41.810318  GET /app/journey/detail  (1820ms, status 200)  req=req_a1b2c3d4
    db                     1130ms (47 queries)
    openai                 420ms
    app                    270ms
    slowest queries:
      880ms  SELECT * FROM journey_stage WHERE journey_id = ? ORDER BY position
External services
Email (Mailgun)1,240 sends this month
Mailgun statusoperational
OpenAI APIreachable
OpenAI spendtracked — within budget
OpenAI statusoperational
Wasabi S3reachable
Monitoring health
  Push alertsconfigured
  Email reports (Mailgun)configured
  Heartbeat (external monitor)configured
  OpenAI checkenabled
  Postgres metricsconfigured
  Alert subscribers1 configured
  All checks executingno internal check errors
One housekeeping item flagged below; everything else is quiet.
CN Watchdog — customernode.com
First-Party AI

1-2 minutes please — Your AI agent is working

First-Party AI™ can make mistakes. Always check important information.