From 0bfe50e7231e227d90ef772e9f1398e9255bfcf9 Mon Sep 17 00:00:00 2001 From: Sluijsens Date: Mon, 19 Oct 2026 11:49:35 +0200 Subject: [PATCH] Adds the monitoring plan and setup for the front-end shell Monitoring reuses the existing Sentry organisation, the self-hosted Umami instance and UptimeRobot, with e-mail alerts. One build serves both environments; the browser picks test or production from the hostname and sends nothing on other hosts. Sentry captures errors only, loads after the page and stores no personal data. Code changes follow after approval. Co-Authored-By: Claude Opus 5.5 --- .../features/frontend-shell/aidlc-state.md | 14 ++- aidlc-docs/features/frontend-shell/audit.md | 72 ++++++++++++++ .../operations/monitoring/monitoring-plan.md | 61 ++++++++++++ .../operations/monitoring/monitoring-setup.md | 78 +++++++++++++++ .../operations/plans/monitoring-setup-plan.md | 95 +++++++++++++++++++ 5 files changed, 315 insertions(+), 5 deletions(-) create mode 100644 aidlc-docs/features/frontend-shell/operations/monitoring/monitoring-plan.md create mode 100644 aidlc-docs/features/frontend-shell/operations/monitoring/monitoring-setup.md create mode 100644 aidlc-docs/features/frontend-shell/operations/plans/monitoring-setup-plan.md diff --git a/aidlc-docs/features/frontend-shell/aidlc-state.md b/aidlc-docs/features/frontend-shell/aidlc-state.md index aa86921..25cf27f 100644 --- a/aidlc-docs/features/frontend-shell/aidlc-state.md +++ b/aidlc-docs/features/frontend-shell/aidlc-state.md @@ -5,7 +5,7 @@ - **Feature Slug**: frontend-shell - **Project Type**: Brownfield - **Start Date**: 2026-10-14T09:46:02Z -- **Current Stage**: OPERATIONS - Deployment Setup (awaiting approval) +- **Current Stage**: OPERATIONS - Monitoring Setup (awaiting approval) - **Branch**: feature/frontend-shell ## Workspace State @@ -40,6 +40,10 @@ - **Included**: Yes - **Method**: CI/CD (Gitea Actions) — test via SSH/scp to Raspberry Pi nginx, production via FTPS to IIS webhost (manual, release/* only) +### Monitoring Setup +- **Included**: Yes +- **Approach**: Combination — Sentry (JS errors), Umami (cookieless visitor stats), UptimeRobot (availability); e-mail alerts; reuses existing services + ## Scope Notes (from user) - Side area / "Info menu" from the static design is OUT of scope (deliberately left out) - E-mail address in the mobile menu is OUT of scope (deliberately left out) @@ -69,14 +73,14 @@ - [x] Build and Test - EXECUTE (complete) ### 🟡 OPERATIONS PHASE -- [~] Deployment Setup - EXECUTE (artifacts generated, awaiting approval) -- [ ] Monitoring Setup - EXECUTE +- [x] Deployment Setup - EXECUTE (approved; pipeline verified, first test deploy green) +- [~] Monitoring Setup - EXECUTE (artifacts generated, awaiting approval) - [ ] Production Readiness Validation - EXECUTE ## Current Status - **Lifecycle Phase**: OPERATIONS -- **Current Stage**: Deployment Setup -- **Next Stage**: Monitoring Setup +- **Current Stage**: Monitoring Setup +- **Next Stage**: Production Readiness Validation ## Reverse Engineering Status - [x] Reverse Engineering - Artifacts generated on 2026-10-14T09:58:04Z (approved 2026-10-14T10:05:21Z) diff --git a/aidlc-docs/features/frontend-shell/audit.md b/aidlc-docs/features/frontend-shell/audit.md index 6503943..485d893 100644 --- a/aidlc-docs/features/frontend-shell/audit.md +++ b/aidlc-docs/features/frontend-shell/audit.md @@ -786,3 +786,75 @@ Verder heb ik de vraag ook beantwoord" **Context**: OPERATIONS - Deployment Setup --- + +## Deployment Setup - Commit/Push Scope + +**Timestamp**: 2026-10-19T07:43:33Z + +**User Input**: "laat mij weten wanneer die klaar is. gezien alles nu lijkt te werken wi lik niet meer dat je zelf commit en pusht. dat was voor het fixen van de pipeline. dese pr kunnen we nu ook gebruiken voor de rest van deze aidlc feature" + +**AI Response**: "Autonomous commit/push withdrawn; only on explicit request from now on. PR #4 stays open for the rest of the frontend-shell AI-DLC feature. Watching run 533 and will report when done." + +**Context**: OPERATIONS - Deployment Setup + +--- + +## Deployment Setup - Approval + +**Timestamp**: 2026-10-19T08:02:45Z + +**User Input**: "ja, zodra hij groen is mag je door naar de monitoring fase" + +**AI Response**: "Run 533 (PR #4, 7750971) green: check and lighthouse succeeded. Deployment Setup marked approved (decision: included; method CI/CD via Gitea Actions, test via SSH/scp to Raspberry Pi nginx, production via FTPS to IIS, manual from release/*). Started OPERATIONS - Monitoring Setup. Found existing monitoring stack in owner's projects (SlpSoftware react-frontend, SlpModularCms): Sentry free tier, self-hosted Umami on the Pi, UptimeRobot." + +**Context**: OPERATIONS - Deployment Setup complete; Monitoring Setup started + +--- + +## Monitoring Setup - Plan and Questions + +**Timestamp**: 2026-10-19T08:03:14Z + +**User Input**: "(none — stage start)" + +**AI Response**: "Created operations/plans/monitoring-setup-plan.md: context (static site; existing Sentry/Umami/UptimeRobot stack in other projects), pre-decided items (one build for both environments, environment from hostname at runtime; narrow CSP exceptions per chosen service generated into web.config/nginx; privacy statement action item), and 7 questions (inclusion, approach, reuse, Sentry delivery without tunnel, Umami, UptimeRobot, alert channels)." + +**Context**: OPERATIONS - Monitoring Setup; awaiting answers + +--- + +## Monitoring Setup - Answers and Artifacts + +**Timestamp**: 2026-10-19T09:23:26Z + +**User Input**: "ik heb de vragen beantwoord" + +**AI Response**: "Answers: Q1 A, Q2 D, Q3 A, Q4 A, Q5 A, Q6 'A, maar gezien er nu ook al een site draait kan ik die nu ook al opzetten voor productie. Voor UptimeRobot hoeven we verder geen code toe te voegen toch?', Q7 A. Confirmed UptimeRobot needs no code; production monitor can start now (watches WordPress until DNS switch), deep-link monitor after go-live. Read SlpSoftware's Sentry init (tunnel via reverse proxy) and UmamiAnalytics (analytics.slpsoftware.nl). Generated operations/monitoring/monitoring-plan.md (M1-M8: hostname-based environment with one build, config in code, direct Sentry without tunnel, lazy Sentry for performance, errors only without PII, separate Umami websites with data-domains and DNT, narrow CSP exceptions, UptimeRobot monitors) and monitoring-setup.md (one-time steps per service, code changes per file, tests, checks after deploy, values needed). Code changes deferred until approval. State updated." + +**Context**: OPERATIONS - Monitoring Setup; awaiting approval + +--- + +## Monitoring Setup - Sentry Plugin + +**Timestamp**: 2026-10-19T09:47:28Z + +**User Input**: "Help me met het opzetten van sentry. org slug: slp-software run code: 8fc9ce6c75" / "ik heb net de sentry agent plugin geinstalleerd. die zou je kunnen gebruiken. ik heb namelijk uitgevoerd `npx @sentry/agent-plugin install slp-software#8fc9ce6c75`" + +**AI Response**: "Read Sentry's instrument playbook: provisioning, DSN retrieval, onboarding progress (run code) and verification all go through the Sentry MCP. Owner installed the Sentry plugin (sentry@claude-plugins-official 1.4.0, MCP https://mcp.sentry.dev/mcp, enabled globally); its tools are not loaded in this already-running session. Advised: restart Claude Code, authenticate via /mcp, start the Sentry setup with a first prompt containing the onboarding code and the M1-M7 constraints (errors only, no tracing/replay, lazy load, hostname-based environment, no PII), on feature/frontend-shell without committing/pushing unasked. Monitoring artifacts and audit entries are uncommitted; offered to commit on request." + +**Context**: OPERATIONS - Monitoring Setup; awaiting session restart for Sentry MCP + +--- + +## Session End - Commit + +**Timestamp**: 2026-10-19T09:49:35Z + +**User Input**: "ik start een nieuwe sessie. de ssh agent. moet die dan ook opnieuw gestart worden? Commit alle wijzigingen voor ik de sessie sluit" + +**AI Response**: "Explained the ssh-agent survives Claude sessions (key lifetime 4h). Committed all pending changes (monitoring plan and setup, monitoring question file with answers, state and audit) on feature/frontend-shell; not pushed." + +**Context**: OPERATIONS - Monitoring Setup; awaiting approval / Sentry setup in a new session + +--- diff --git a/aidlc-docs/features/frontend-shell/operations/monitoring/monitoring-plan.md b/aidlc-docs/features/frontend-shell/operations/monitoring/monitoring-plan.md new file mode 100644 index 0000000..0d14400 --- /dev/null +++ b/aidlc-docs/features/frontend-shell/operations/monitoring/monitoring-plan.md @@ -0,0 +1,61 @@ +# Monitoring Plan — frontend-shell + +Decisions: [monitoring-setup-plan.md](../plans/monitoring-setup-plan.md) (Q1 = A, Q2 = D, Q3 = A, Q4 = A, Q5 = A, Q6 = A + production now, Q7 = A). + +## Overview + +```mermaid +graph LR + Visitor["Visitor browser"] -->|"JS errors"| Sentry["Sentry (EU), existing org"] + Visitor -->|"page views, cookieless"| Umami["Umami on the Pi, analytics.slpsoftware.nl"] + Uptime["UptimeRobot"] -->|"HTTP checks"| Site["andreaslop.nl and test.andreaslop.nl"] + Sentry -->|"e-mail, new error type"| Owner["Owner"] + Uptime -->|"e-mail, site down"| Owner + + classDef visitor fill:#f6e05e,stroke:#c05621,stroke-width:1px,color:#000; + classDef service fill:#e9d5ff,stroke:#6b21a8,stroke-width:1px,color:#000; + classDef site fill:#9ae6b4,stroke:#2f855a,stroke-width:1px,color:#000; + classDef owner fill:#63b3ed,stroke:#2b6cb0,stroke-width:1px,color:#000; + + class Visitor visitor; + class Sentry,Umami,Uptime service; + class Site site; + class Owner owner; +``` + +Text alternative: visitors' browsers send JavaScript errors to Sentry and cookieless page views to Umami; UptimeRobot checks both sites from outside; Sentry and UptimeRobot e-mail the owner. + +## Chosen Approach (all three, reusing existing services) + +| Area | Service | What it covers | Code needed | +|---|---|---|---| +| **Logging** | **Sentry** (existing EU organisation, new project `andreaslop-fotografie`) | JavaScript errors in visitors' browsers: render errors caught by `ErrorPage` and unhandled errors, tagged `test` or `production` | Yes | +| **Dashboards: visitors** | **Umami** (existing install on the Pi, two new "websites": test and production) | Page views, referrers, devices, without cookies or personal data | Yes | +| **Dashboards: availability** | **UptimeRobot** (existing account, new monitors) | Whether test and production respond; response time history | No | +| **Alerting** | Sentry + UptimeRobot defaults | E-mail on a **new** type of error (Sentry) and when a site is **down** (UptimeRobot) | No | + +## Key Decisions + +| # | Decision | Why | +|---|---|---| +| M1 | **One build for both environments**: the browser picks the environment from the hostname (`andreaslop.nl` → production, `test.andreaslop.nl` → test). Any other host (localhost, Lighthouse CI, previews) sends **nothing**. | Keeps "deploy exactly what was tested" (D-pipeline). Local runs and CI never pollute the dashboards. | +| M2 | **Sentry and Umami settings live in code** (`src/monitoring/config.ts`), not in Gitea variables. | The Sentry DSN and Umami website IDs are public by design: they end up in every visitor's browser anyway. In code they are reviewed, tested and versioned. | +| M3 | **Sentry sends directly** to `*.ingest.de.sentry.io` (no tunnel). | Q4 = A: the IIS host serves only static files until the .NET API exists; some errors from visitors with ad-blockers are missed. Follow-up: tunnel via the API. | +| M4 | **Sentry loads after the page**, not in the main bundle. | Keeps the performance budget: the home page on mobile already sits just above its 0.8 target. Errors are queued until Sentry is ready. | +| M5 | **Sentry: errors only.** No performance tracing, no session replay, no personal data (`sendDefaultPii: false`, IP storage off in the project settings). | Smallest bundle, least data, simplest privacy story. | +| M6 | **Umami: separate websites for test and production**; `data-domains` restricts counting to the right hostname, and `data-do-not-track` respects the browser's Do Not Track setting. | Test traffic never mixes with real numbers. | +| M7 | **CSP exceptions as narrow as possible**, generated into `web.config` and the nginx config like the other headers. | Nothing else is opened. | +| M8 | **UptimeRobot**: production monitor now (it watches the current WordPress site until the DNS switch, then the new site automatically), test now, and the `/portfolio` deep-link monitors. | Q6 = A, owner: production can start now. | + +## Explicitly Out of Scope +- Sentry tunnel against ad-blockers: comes with the .NET API (follow-up). +- Server-side logging (nginx, IIS): not managed by this project. nginx logs on the Pi and the hoster's IIS logs stay where they are. +- Performance tracing, session replay, custom Umami events. +- Alerts other than e-mail. + +## Privacy (action item for the privacy statement page) +The privacy statement (still a placeholder) must mention: +- **Umami**: anonymous, cookieless visit statistics, self-hosted in the Netherlands, no personal data. +- **Sentry**: technical error reports, sent to Sentry (EU region) without IP address or personal data. + +Umami without cookies needs no cookie banner under the Dutch DPA's guidance for analytics that are set up privacy-friendly. Sentry error reporting falls under legitimate interest. **This is not legal advice; check it when writing the privacy statement.** diff --git a/aidlc-docs/features/frontend-shell/operations/monitoring/monitoring-setup.md b/aidlc-docs/features/frontend-shell/operations/monitoring/monitoring-setup.md new file mode 100644 index 0000000..a2776b1 --- /dev/null +++ b/aidlc-docs/features/frontend-shell/operations/monitoring/monitoring-setup.md @@ -0,0 +1,78 @@ +# Monitoring Setup — frontend-shell + +What to do once in each service, and what changes in the code. The code changes are made on PR #4 after approval of this setup. Until the values below are filled in, the site sends nothing (safe default). + +## 1. Sentry (logging + error e-mails) + +### In Sentry (once) +1. In your existing organisation, create a project: platform **React**, name `andreaslop-fotografie`. +2. Copy the **DSN** (Settings → Client Keys). It looks like `https://@o4511795618185216.ingest.de.sentry.io/`. +3. **Settings → Security & Privacy**: turn on **"Prevent Storing of IP Addresses"** (M5). +4. **Alerts**: keep the default rule "A new issue is created" → e-mail to you (Q7 = A). Environments `test` and `production` appear automatically after the first event. + +### In the code (after approval) +| File | Change | +|---|---| +| `package.json` | Add `@sentry/react` (same package as SlpSoftware) | +| `src/monitoring/config.ts` (new) | `sentryDsn` (from step 2) and `monitoringFor(hostname)` → `{ environment, umamiWebsiteId }` or `null` for unknown hosts (M1) | +| `src/monitoring/sentry.ts` (new) | `startSentry()`: loads `@sentry/react` dynamically after the `load` event (M4); `init` with `environment`, `release` (commit SHA from the build), `sendDefaultPii: false`, no tracing or replay. `reportError(error)`: queues errors until Sentry is ready. | +| `src/main.tsx` | Calls `startSentry()` | +| `src/components/StatusPage/ErrorPage.tsx` | Besides `console.error`, also `reportError(error)` (BR-ERR-03 extended) | +| `config/securityHeaders.ts` | `connect-src` + Sentry ingest host (M7); regenerated into `web.config` and nginx | +| Workflow `check` job | Build with `VITE_RELEASE=${{ github.sha }}` so Sentry shows which release an error came from | + +### Check after deploy +On `https://test.andreaslop.nl`, run in the browser console: +```js +setTimeout(() => { throw new Error('Sentry-test vanaf test') }) +``` +The error appears in Sentry under environment `test` within a minute, and you get an e-mail for the new issue. + +## 2. Umami (visitor dashboard) + +### In Umami (once) +1. Log in at `https://analytics.slpsoftware.nl`. +2. **Settings → Websites → Add website**, twice: + - name `Andrea Slop Fotografie`, domain `andreaslop.nl` + - name `Andrea Slop Fotografie (test)`, domain `test.andreaslop.nl` +3. Copy both **Website IDs** (a UUID per website). + +### In the code (after approval) +| File | Change | +|---|---| +| `src/monitoring/config.ts` | The two website IDs, one per hostname (M6) | +| `src/components/Analytics/UmamiAnalytics.tsx` (new) | Adds `https://analytics.slpsoftware.nl/script.js` with `data-website-id`, `data-domains=` and `data-do-not-track="true"`, only for a known hostname (M1). Same pattern as SlpSoftware's `UmamiAnalytics`. | +| `src/components/AppShell.tsx` | Renders `UmamiAnalytics` | +| `config/securityHeaders.ts` | `script-src` and `connect-src` + `https://analytics.slpsoftware.nl` (M7) | + +### Check after deploy +Open `https://test.andreaslop.nl`. In Umami, the test website shows a visitor under "Realtime". If you have Do Not Track switched on in your browser, you won't see yourself; that is expected. + +## 3. UptimeRobot (availability + down e-mails) + +No code needed. Create these monitors in your existing account (type **HTTP(s)**, interval 5 minutes, alert contact: your e-mail): + +| Monitor | URL | When | +|---|---|---| +| Andrea Slop — test | `https://test.andreaslop.nl/` | Now | +| Andrea Slop — test — deep link | `https://test.andreaslop.nl/portfolio` | Now (checks the SPA fallback) | +| Andrea Slop — productie | `https://andreaslop.nl/` | **Now**. It watches the current WordPress site until the DNS switch, and the new site after that. | +| Andrea Slop — productie — deep link | `https://andreaslop.nl/portfolio` | **After go-live**. On WordPress this URL may not exist and would give false alarms. | + +Optional: type **Keyword** with the keyword `Andrea Slop Fotografie`. That catches an empty or wrong page that still answers 200; the word is in the static HTML of the new site. + +## 4. Tests (part of the code changes) +- **`monitoringFor`**: example tests for each known hostname, plus a property test that every other hostname (random strings, `localhost`, IP addresses) returns `null` (PBT-03 invariant). +- **`UmamiAnalytics`**: no script for an unknown host; the right `data-website-id` and `data-domains` for each known host; only one script element. +- **`reportError`**: errors before initialisation are queued and sent once Sentry is ready; nothing is sent for an unknown host. +- **`securityHeaders`**: the production CSP contains exactly these two external hosts, in the right directives only, and no wildcards. +- **`serverConfig`**: drift test; `web.config` and nginx contain the new CSP. + +## 5. Values needed from you +Fill these in after steps 1 and 2. Placeholders are fine to start with; monitoring stays off until they are set. + +| Value | From | +|---|---| +| Sentry DSN | Sentry, step 1.2 | +| Umami website ID, production | Umami, step 2.3 | +| Umami website ID, test | Umami, step 2.3 | diff --git a/aidlc-docs/features/frontend-shell/operations/plans/monitoring-setup-plan.md b/aidlc-docs/features/frontend-shell/operations/plans/monitoring-setup-plan.md new file mode 100644 index 0000000..e147771 --- /dev/null +++ b/aidlc-docs/features/frontend-shell/operations/plans/monitoring-setup-plan.md @@ -0,0 +1,95 @@ +# Monitoring Setup Plan — frontend-shell + +## Context + +- **What runs**: a static site (no back-end), deployed to test (Raspberry Pi, nginx) and later production (IIS webhost). See [deployment-plan.md](../deployment/deployment-plan.md). +- **Current state**: no monitoring in this project. Errors only go to the browser console (`ErrorPage`, BR-ERR-03). +- **Existing stack in your other projects** (SlpSoftware `react-frontend`, SlpModularCms): + - **Sentry** (free tier): JavaScript errors + - **Umami**, self-hosted on the Pi: visitor statistics without cookies + - **UptimeRobot**: is the site reachable +- **Already decided** (no question needed): + - **One build for both environments stays.** Test vs production (for example for Sentry or Umami) is determined in the browser from the hostname, not with a separate build. The pipeline keeps deploying exactly the same build that was tested. + - **External monitoring services need CSP exceptions.** The current CSP only allows the site's own origin. Each external service you choose is added to `config/securityHeaders.ts`, and from there to `web.config` and the nginx config, as narrowly as possible (only that host, only the directive that needs it). + - **Privacy statement.** Whatever measures visitors must later be mentioned there. The page is still a placeholder, so this becomes an action item for that page. + +## Plan + +- [x] 1. Answer the questions below +- [x] 2. Analyze answers (follow-up questions if needed) +- [x] 3. Generate `operations/monitoring/monitoring-plan.md` +- [x] 4. Generate `operations/monitoring/monitoring-setup.md` (and, if needed, code and config changes on this PR after your approval) +- [ ] 5. Update CSP, server config, tests and privacy action items for the chosen services + +--- + +## Questions + +Vul per vraag de letter in na `[Answer]:`. Past geen enkele optie, kies dan de laatste (Anders) en licht toe. Waar ik een voorkeur heb staat **(aanbevolen)**. + +### Vraag 1: Monitoring opzetten voor deze feature? + +A) Ja, help me monitoring op te zetten +B) Nee, dit sluit aan op bestaande monitoring of valt nu buiten de scope +C) Weet ik niet, stel een aanpak voor en ik beslis +X) Anders (beschrijf hieronder na de [Answer]:-tag) + +[Answer]: A + +### Vraag 2: Welke vormen van monitoring? + +A) Logging: JavaScript-fouten bij bezoekers vastleggen +B) Meldingen: een bericht als de site plat ligt of er fouten optreden +C) Dashboards: bezoekersstatistieken en een overzicht van de beschikbaarheid +D) Een combinatie, namelijk alle drie, net als je andere projecten **(aanbevolen)** +X) Anders (beschrijf hieronder na de [Answer]:-tag) + +[Answer]: D + +### Vraag 3: Bestaande diensten hergebruiken? + +A) Ja: hetzelfde Sentry-account (een nieuw project of een eigen omgeving), dezelfde Umami-installatie op de Pi (nieuwe "websites" voor test en productie) en hetzelfde UptimeRobot-account (nieuwe monitors) **(aanbevolen)** EÊn plek om alles te bekijken, geen extra kosten. +B) Aparte, nieuwe accounts of installaties voor deze site +X) Anders (beschrijf hieronder na de [Answer]:-tag) + +[Answer]: A + +### Vraag 4: Hoe komen JavaScript-fouten bij Sentry? + +De site is statisch. In SlpSoftware loopt Sentry via een eigen doorgeefluik ("tunnel") langs adblockers, maar daarvoor is een server-onderdeel nodig. Bij de webhoster draait alleen IIS met statische bestanden, tot de .NET API er is. + +A) Nu rechtstreeks naar Sentry. De CSP krijgt alleen het ingest-adres van Sentry erbij (`connect-src`). Een deel van de fouten mist bij bezoekers met een adblocker. De tunnel komt later via de .NET API. **(aanbevolen)** +B) Nog geen Sentry. Fouten alleen in de browserconsole, Sentry pas met de API. +X) Anders (beschrijf hieronder na de [Answer]:-tag) + +[Answer]: A + +### Vraag 5: Bezoekersstatistieken met Umami + +Umami gebruikt geen cookies en slaat geen persoonsgegevens op. Daarmee is volgens de Autoriteit Persoonsgegevens meestal geen cookiebanner nodig, mits het zo ingesteld is. + +A) Ja, met de bestaande Umami op de Pi. Aparte "websites" voor test en productie, zodat testverkeer niet in de echte cijfers komt. De CSP krijgt het Umami-adres erbij (`script-src` en `connect-src`). **(aanbevolen)** +B) Alleen voor productie, niet voor test +C) Nog geen statistieken +X) Anders (beschrijf hieronder na de [Answer]:-tag) + +[Answer]: A + +### Vraag 6: Beschikbaarheid bewaken met UptimeRobot + +A) Monitors op test nu, en op productie zodra de DNS omgezet is. Ze controleren de homepage en een deep link (`/portfolio`, om de SPA-fallback te testen). **(aanbevolen)** +B) Alleen productie, na de livegang +C) Geen beschikbaarheidsbewaking +X) Anders (beschrijf hieronder na de [Answer]:-tag) + +[Answer]: A, maar gezien er nu ook al een site draait kan ik die nu ook al opzetten voor productie. Voor UptimeRobot hoeven we verder geen code toe te voegen toch? + +### Vraag 7: Meldingen + +A) E-mail van UptimeRobot als de site plat ligt, en e-mail van Sentry bij een nieuw soort fout (hun standaardmeldingen) **(aanbevolen)** +B) Alleen bij een storing (UptimeRobot), niet bij fouten +C) Geen meldingen, ik kijk zelf in de dashboards +D) Een ander kanaal (bv. Telegram, ntfy, Teams); beschrijf welk na de [Answer]:-tag +X) Anders (beschrijf hieronder na de [Answer]:-tag) + +[Answer]: A