What problem does it solve? Worker and background-service deployments on Azure App Service often fail during startup before Application Insights initializes, leaving no logs to diagnose the failure. This Skill defines a complete, source-controlled observability baseline so failures are captured through both durable centralized telemetry and short-lived filesystem diagnostics. ## Core Features & Use Cases - Six-part observability baseline: Application Insights wiring before hosted services, diagnostic settings to a durable sink, bounded non-production filesystem logging, detailed errors, failed-request tracing, and reversible escalation controls. - Infrastructure as Code templates: Bicep examples for App Service log configuration and diagnostic settings, with platform-aware handling of Windows-only features on Linux or container deployments. - Temporary escalation contract: Source-controlled diagnostic escalation with owner, incident identifier, UTC expiry, bounded retention, and an explicit rollback to off. - Use Case: A .NET 8 BackgroundService on Windows App Service dies intermittently at startup with no Application Insights data. Use this Skill to add early host telemetry wiring, enable bounded filesystem logging in non-production, and verify the failure is captured with correlation data. ## Quick Start Ask the agent to review your App Service worker deployment and produce the application wiring and Bicep changes needed for a complete observability baseline.
