ChurchServe Angular Tutorial Part 26-2: OpenTelemetry and Production Operations
Instrument ChurchServe with structured JSON logs, ASP.NET Core traces, runtime metrics, an optional OTLP exporter, and release-level operational checks.
Instrument ChurchServe with structured JSON logs, ASP.NET Core traces, runtime metrics, an optional OTLP exporter, and release-level operational checks.
Add bounded Angular telemetry, end-to-end correlation IDs, safe global error reporting, and a protected ASP.NET Core ingestion endpoint.
Serve the combined ChurchServe artifact with health probes, safe SPA routing, cache and security headers, executable smoke tests, and CI retention.
Load validated public configuration before Angular starts and package the optimized client with ASP.NET Core as one repeatable ChurchServe artifact.
Protect ChurchServe’s highest-value journeys with Playwright, isolated SQLite fixtures, accessible locators, and actionable CI failure evidence.
Connect Angular validation errors to fields, preserve focus during optimistic assignments, announce status changes, and add automated accessibility scans.
Give ChurchServe one clear main landmark, semantic schedule lists, predictable focus after Angular navigation, visible focus indicators, and reduced-motion support.
Minimize volunteer data, preserve Angular’s safe rendering path, test hostile input and denied operations, and define production security boundaries.
Validate session permissions, guard lazy routes, hide unavailable actions, and clear cached state when a user’s capabilities change.
Separate authentication from authorization with capability claims, ASP.NET Core policies, protected Minimal API endpoints, and denial tests.