{"version":"2.1.242","anchor":"telemetry-for-hook-templates-and-expired-leases","canonical_anchor":"telemetry-for-hook-templates-and-expired-leases","heading":"Telemetry for hook templates and expired leases","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/telemetry-for-hook-templates-and-expired-leases","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Telemetry for hook templates and expired leases\n\nThree more telemetry shapes cover hook template runs, uploads and expiring registrations.\n\n**What**\n\nThree more event shapes cover the template path: a per-run event with template id, outcome, duration and dropped fields; an upload event with outcome, template and byte count; and one for a registration lease expiring. Emitted only from the gated device-hook handlers.\n\n**Details**\n\n- The existing registration event gained a count of templates installed alongside those awaiting upload and those refused.\n- It also records how long the handler waited for the account flags, capped at 5000 ms, and whether it shared an already in-flight flag read.\n\n**Evidence**\n\n`tengu_device_hook_template_upload`\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}