Rond Sentry logging-follow-up af: bevestigd werkend, documentatie bijgewerkt
Continuous Integration / config (pull_request) Successful in 11s
Continuous Integration / prepare (pull_request) Successful in 1m15s
Continuous Integration / build (pull_request) Successful in 1m54s
Continuous Integration / test (pull_request) Successful in 1m47s
Continuous Integration / deploy-test (pull_request) Skipped

Co-authored-by: Junie <junie@jetbrains.com>
This commit is contained in:
2026-07-25 16:05:56 +02:00
co-authored by Junie
parent 708d89905c
commit 9732791d09
5 changed files with 17 additions and 5 deletions
@@ -69,7 +69,7 @@ Pick one:
| Concern | Approach | Status |
|---|---|---|
| Client-side errors | Logging (console + Sentry free tier) | Implemented; `VITE_SENTRY_DSN` Gitea variable still needs to be created by the user |
| Client-side errors | Logging (console + Sentry free tier, incl. tracing, environment/release tags, and an ad-blocker-proof tunnel) | Implemented and confirmed working end-to-end (errors, logs, and metrics received) locally and on the test environment; the `VITE_SENTRY_DSN` Gitea repository variable still needs to be created by the user for the test/production build to report to Sentry (local already works via `.env.local`) |
| Visitor/usage insight | Analytics dashboard (Plausible/Umami/GA4) | Tool selection open item |
| Site reachability | Uptime dashboard (UptimeRobot/Better Uptime) | Tool selection + production URL open item |
| Alerting | Out of scope | Not configured |