Operations & Administration (Control)
Launch health and diagnostics
PerGestore
A checklist of whether the installation is ready to launch — red blockers, yellow warnings, a real test of email delivery — and the diagnostics page with tools and live status.
A cosa serve#
Before a launch (new customer, new instance, pilot) nothing should fail because of a missing setting — and in operation, locked sessions and a failed service should be quick to find.
Come funziona#
Percorso di clicAdministrationDiagnostics
- 1Open “Launch health” under /admin/launch-health (also linked on the page “Access codes”). At the top: “No open blockers — ready to launch” or the number of open blockers.
- 2The table: per checkpoint status (green, red = blocker, orange = warning), name and detail (Fig. 1).
Fig. 1 The checkpoints with status (green, warning, blocker), name and detail. - 3“Test email delivery live”: enter a recipient and “Send test email” — confirms the whole sending route, not just the key.
- 4“Diagnostics” (tile on the home page; address /diagnostics, the old address in the administration redirects there): tabs “Tools” and “Uptime”.
- 5“Tools”: “Check speech recognition” queries the active EU service and reports whether the key is set and accepted — the page never shows the key itself. The fallback service outside the EU only appears if it has been explicitly switched on, and then with a warning. Next to it “Unlock all locked sessions” — unlocks sessions that have reached their usage limit and resets their counters.
- 6“Uptime”: “Live system health” with “Check now” — overall status, version, environment, response time and the dependencies; plus two addresses for external monitoring.
Impostazioni e interruttori#
Nessun interruttore proprio nel catalogo — la funzione fa parte del suo contesto.
The checkpoints#
- Database reachable (blocker)
- Table of access codes present (blocker)
- Redemption function present — checked with a non-existent code that uses up nothing (blocker)
- Access codes with remaining redemptions available, counted across all courses and broken down per course (warning — without codes enrolment runs via other routes)
- Stuck enrolments (warning)
- Email sending set up (blocker)
- Secret for background runs set (warning)
Who may do what#
- Launch health: only the operator.
- Diagnostics, speech recognition check and unlocking: only the operator — both affect the whole installation.
Suggerimenti#
- A red blocker prevents the launch, an orange warning does not.
- For external monitoring: have the light address (“liveness”, answers without a database) pinged every 1 to 5 minutes, the thorough one (“readiness”) less often.
Funzioni correlate#
- IT control centreThe operational view in real time: database, avatar machines, render pipeline, live avatar and services — refreshed every five seconds, with status in colour, word and symbol.
- Access codes and voucher healthCodes with which someone enrols in a course without payment — with a maximum number of redemptions and a sending link; plus a list of stuck enrolments that can be redeemed afterwards at the push of a button.
- Cost recording and usage limitsEvery call to an external service goes through one single recording point; limits apply in stages.