{"version":"2.1.242","anchor":"six-new-device-hook-telemetry-events-none-of-which-can-fire-","canonical_anchor":"six-new-device-hook-telemetry-events-none-of-which-can-fire-","heading":"Six new device-hook telemetry events, none of which can fire yet","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/six-new-device-hook-telemetry-events-none-of-which-can-fire-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Six new device-hook telemetry events, none of which can fire yet\n\nSix telemetry events for machine-run cloud hooks exist but cannot fire in this build.\n\n**What**\n\nThe machine-side hook client reports each forwarded hook it serves and each registration attempt, plus consent notices, lapse lines and pinning outcomes. All of it sits behind the device-hooks gate that returns false in this build.\n\n**Details**\n\n- `tengu_device_hook_served` carries event, kind, outcome, exit class, duration, whether paths were translated, and whether the run was a replay, blocked, staged, repinned, or waited.\n- `tengu_device_hooks_client_register` carries outcome, trigger, counts of forwarded, templates, held and accepted or ignored entries, and attempt number.\n- Also `tengu_device_hooks_consent_notice`, `tengu_device_hooks_lapse_line`, `tengu_device_hooks_reach_pinned`, `tengu_device_hooks_source_pinned`.\n- Successful lease renewals are deliberately not reported.\n- None of these names exist in 2.1.241.\n\n**Evidence**\n\n`tengu_device_hook_served`\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}