QUOX backup status is CRITICAL: daily backup was skipped because a systemd condition was not met; newest snapshot is 498.7 hours old. QUOX filesystem usage is at most 34.5%, and QUOX memory use is 42.0%; QUOX has no measured resource saturation. QUOX failed units: none. QUOX security scanner state requiring review: no current scanner warnings. These findings require triage but do not by themselves establish broad system instability or compromise.

QUOX: uptime is 2d 22h 1m; load averages are 5.81884765625 / 5.1103515625 / 4.4990234375 across 56 CPUs. Memory use is 42.0% and swap use is 0.0%. Filesystems: / 34.5% used. During this reporting window QUOX recorded 42 important events: service failure=42. Security-log observations total 0 total (0 scanner items; 0 other security-log observations).

TINMAN: current Wazuh telemetry reports 4.4% CPU, 78.2% memory used, and volumes B: 70.7% used, C: 29.6% used, D: 55.7% used.

Wazuh: service state is HEALTHY; enrolled agents are TINMAN: active, QUOX: active. It recorded 248 level-10-or-higher alerts in the last 24 hours, attributed as TINMAN: 220, QUOX: 28.

QUOX backups: daily backup was skipped because a systemd condition was not met; newest snapshot is 498.7 hours old Action: Restore scheduled backup operation.

TINMAN backups: CRITICAL: The TINMAN backup schedule is overdue; the last success was 19.6 days ago; last success 2026-08-26T15:00:54.0054940Z; schedule overdue true; no backup job is currently running; Backup Repository has 29.3% free.

Updated 2026-09-15T06:04:47Z. Reporting window 2026-09-14T06:04:47Z to 2026-09-15T06:04:47Z. AI narrative: available and constrained by measured state.