Files
obsidian-vault/work/projects/cpm-pr0-episode-telemetry-summary-2026-10-16.md
T

3.8 KiB
Executable File

title, date, tags
title date tags
CPM PR0 — complete telemetry change 2026-10-16
work
cpm
telemetry

CPM PR0: one terminal report per failure episode

Proposed change:

Replace separate init_failed, stuck, recovery[with/without reload] and CPM post-reload-failure events with web_extension_cpm_episode. Each report contains the initial failure and its observed outcome, so diagnosis no longer allows joining a sequence of events.

When it fires:

The first 4s timeout opens an episode and captures one diagnostic snapshot.

Later failures and reloads update local state. A qualifying dashboard response or a five-minute deadline closes the episode and emits one logical report. The deadline works without further navigations. Existing stuck detection and automatic reload behavior are preserved.

Attribution:

Five added summary parameters:

  • reason: the first timeout's context — session_restoration, tab_crash, extension_reload or other. Previously encoded in failure pixel names.

  • was_stuck: whether a later eligible non-restoration navigation, begun after the first failure, also timed out.

  • outcome: failed_measurement_response for the measurement that timed out; failed_tab_response for a later measurement on a failing tab; other_tab_response for another tab; unattributed_response for an ambiguous current-document match; or no_response_before_deadline.

  • reload_state: none (no reload observed), pending (replacement started), failed (replacement failed), loaded (replacement loaded), or response_timed_out (its first eligible messaging measurement timed out). Loaded alone does not prove messaging recovery.

  • response_after: elapsed time since the first failure, bucketed as under_30s, 30s_to_1m or 1m_to_deadline. Omitted for the no-response outcome.

Eight existing diagnostic booleans from ✓ TD: CPM failure pixels attribution: all are captured at the first failure; unavailable facts are omitted.

  • context_loaded — extension context loaded; bg_view_alive — current background view exists.

  • bg_process_alive — its process is alive; bg_process_responsive — WebKit considers it responsive.

  • tab_in_context — failing tab registered in WebKit; handler_registered — autoconsent native handler registered.

  • tab_controller_match — tab and context controllers match; tab_has_ext_scripts — extension scripts remain registered.

bg_events is kept included, using the existing encoder: the latest 12 events at the first failure, oldest first, as sanitized token@age entries. Ages use 30s, 1m, 2m, 5m, 15m and over_15 buckets; older entries are dropped to keep the value within 255 characters. The timeline can contain error descriptors. Later failures and recovery do not replace or append to this snapshot.

Standard metadata remains: appVersion on both platforms, plus pixelSource and channel on macOS.

Remove retired pixels from ✓ TD: CPM failure pixels attribution:

  • debug_web_extension_cpm_initialization_failed_after_session_restoration

  • debug_web_extension_cpm_initialization_failed_after_other

Parameters removed from transmission:

context_errors, network_restarted, critical_memory_age, bg_view_creations, bg_view_leaked_count, app_version_change, app_launch_age, background_graveyard_enabled and recovery_from. Episode state and response attribution replace recovery_from. Graveyard attribution is also removed from the diagnostic model and monitor.