# Monitoring Plan - andreaslop-site-hosting (test) - **Approach** (Q2 = D): logging plus alerting on tooling that already exists; no new dashboards (Q5 = A), no central log aggregator (Q3 = A). - **Tooling reused**: systemd/journald on the Pi (host logs), the Andrea Slop Fotografie **website's** existing Sentry project (Q3 = B in U2; NOT SlpSoftware's admin project), the host's `/health` endpoint (already checked by every deploy), the admin's same-origin `/sentry-tunnel`. - **Covered**: host errors and security events (Sentry), 301/404 website lines (journald), browser errors from the admin (via the tunnel), liveness (`/health` after each deploy and optionally an uptime monitor). - **Not covered / known gaps**: no performance dashboard or latency alerting; the website's own browser errors are reported by the website itself; Sentry events from website, host and admin share one project, separated by the `environment` tag (`test`) and URL; test only, production monitoring comes with a future production setup. - **Verification**: after the first deploy, trigger one wrong setup token and one 404 and confirm they show up (see `monitoring-setup.md`, section 4).