Diagnose observability destinations independently

An empty observability view is evidence about that view, not every signal in the system. Verify project identity, bounded counts, and latest timestamps separately for analytics events, exceptions, logs, traces, and any exporter destination. Then inspect routing and deliberate capture exclusions. Fresh arrivals in one product establish partial pipeline health, not lossless delivery elsewhere.

Applicability: systems that send different signal classes to different vendors or products. Limits: repository configuration is only a routing intent; current deployment and collection state require live verification.

Evidence basis (2026-09-18): repository documentation and browser-runtime source showed that operational logs and browser analytics had intentionally different routes and capture settings. The original live event counts and empty-view observation lacked a retained telemetry artifact and are omitted.