{"version":"2.1.223","anchor":"telemetry-run-files-are-filtered-by-extension-during-collect","canonical_anchor":"telemetry-run-files-are-filtered-by-extension-during-collect","heading":"Telemetry run files are filtered by extension during collection","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/telemetry-run-files-are-filtered-by-extension-during-collect","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Telemetry run files are filtered by extension during collection\n\nTelemetry collection skips non-JSON files instead of trying to parse them.\n\n**What**\n\nThe walker that gathers telemetry data skips non-JSON files instead of attempting to parse them.\n\n**Details**\n\n- The recursive directory walker gained an options bag with an `entryMatcher` predicate.\n- The telemetry `runs` directory is walked with `entryMatcher: (i) => i.endsWith(\".json\")`.\n\n**Evidence**\n\n`entryMatcher: (i) => i.endsWith(\".json\")`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}