Logs & Monitoring
Chinaski gives you several observation surfaces: the system journal (with structured JSON security events), in-app log views (event log, auth log, build history), multi-check health endpoints for external monitoring, and a metrics summary. This page indexes the pieces and links to each subpage:
- System logs (journald & security events): where logs land, the JSON event lines, PII/retention guidance, and the optional external security log.
- In-app log views: event log, auth history, build history and the metrics dashboard.
- Health checks & monitoring:
/health,/api/health, and how to wire them into uptime monitoring.
The quick answers
- Logs live in systemd-journald (
journalctl -u chinaski@<N> -f), with high-signal events additionally emitted as machine-readable JSON lines on the same stream (grep '"event"'isolates them). - The build trail is in-app, not in journalctl alone: build history keeps per-run logs, per-phase timings, and validation results.
- External monitors should target the health endpoint; the project ships a 5-minute cron monitor for build success and page presence as a ready-made template.
- Sensitive data (client IPs) travels in the log fields; README includes a journald retention-policy snippet and advises matching retention in any external SIEM.
In this section
Also in Logs & Monitoring
Use the two unauthenticated health endpoints and the in-app health dashboard: what GET /health checks and how to wire it into monitoring.
The admin area's in-app logs: the Health page event log, authentication history, and the build history of the last 100 builds, with their filters.
Read Chinaski logs in the systemd journal, the structured JSON security events and their fields, the optional append-only file, and retention notes.