Health Checks, Telemetry, and Event Instrumentation
Diagnostics provide a comprehensive snapshot of system health: static assets availability, database connectivity, environment versions, and network resolution. The analytics layer adds visibility into how users interact with the site, including social shares, button clicks, and feature invocations. Together, they support iterative improvement and production stability. This page explains how to read the diagnostics API, how GTM is injected into pages via a dynamic config endpoint, and how to validate performance across devices.
The diagnostics API returns status for static checks like index or favicon availability, database probes, environment versions, and STUN DNS resolution for WebRTC. A healthy result indicates that the baseline services are online. If the status is degraded, the page highlights the cause, such as missing static assets or database errors. By linking diagnostics to the Builder Agent, issues discovered during deployment are immediately converted into tasks to fix, test, and verify.
Analytics are unified through Google Tag Manager. Instead of hardcoding identifiers into pages, the site references a small dynamic script, `/config.js`, which sets `window.GTM_ID` from server environment variables. This makes production updates simple and consistent. Pages also log social share events and critical interactions to the server analytics endpoint for audits. The combined approach ensures both client‑side metrics and server‑side records remain aligned.
Capabilities
Unified Health Checks
One endpoint surfaces critical readiness signals for production operations.
Environment‑Driven Analytics
Pages ingest GTM ID at runtime through `/config.js` without code rewrites.
Share and Interaction Events
Client events are captured for visibility and improvement planning.