Skip to content
LogScope Docs

v0.5.16

Released: 2026-05-12

Telemetry pipeline repair after a 25-day silent outage. No user-facing functionality changes.

Fixed

Section titled “Fixed”
  • Telemetry routing repointed to a fresh Azure Application Insights resource. On 2026-04-17 the previous workspace-based App Insights component entered a “silent-drop” state: the ingestion endpoint kept returning HTTP 200 with itemsAccepted=1, but the Log Analytics workspace stopped storing events. The package’s internal HTTPS layer swallows 400-class failures silently, so the outage went undetected for 25 days. v0.5.16 ships a new connection string pointing at a freshly provisioned resource (Bluefield flow type, dedicated Log Analytics workspace) that is verified end-to-end.

Added

Section titled “Added”
  • Non-silent telemetry catch block. Synchronous send failures now log to the LogScope output channel once per session via logger.logError instead of being silently swallowed. Note: this does not catch async HTTP failures inside the @vscode/extension-telemetry package; those still need to be detected via the upstream GitHub Action.
  • Daily GitHub Action health check (.github/workflows/telemetry-health.yml). POSTs a synthetic event to App Insights every day at 13:00 UTC and (when the APPINSIGHTS_API_KEY secret is configured) verifies the event lands in the workspace. Workflow failure auto-emails repo admins, providing 24-hour detection on the same fault mode that took 25 days to spot last time.