{"version":"2.1.242","anchor":"telemetry-for-the-git-based-directory-sync-engine","canonical_anchor":"telemetry-for-the-git-based-directory-sync-engine","heading":"Telemetry for the git-based directory sync engine","tier":"internal","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/telemetry-for-the-git-based-directory-sync-engine","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Telemetry for the git-based directory sync engine\n\nDirectory sync reporting now names the engine used and adds six git-engine events; syncing itself is unchanged.\n\n**What**\n\nDirectory sync push and pull events now record which engine ran and git-specific counters, and six new events cover the git engine's lifecycle. This is reporting only; nothing about syncing changes.\n\n**Details**\n\n- New counters include bundle size in bytes, commit count, prerequisites, withdrawn installs, held-back deletes, parked overflow and skipped rounds.\n- New events: git open (carrying the branch fast-forward rule and whether an upload happens at open), fast forward, peer silent, uploads not taken, unreachable, and reachable again.\n\n**Evidence**\n\n`tengu_dir_sync_git_uploads_not_taken`\n\n- Area: Directory Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}