{"version":"2.1.223","anchor":"first-party-event-logging-exporter-takes-a-storage-backend","canonical_anchor":"first-party-event-logging-exporter-takes-a-storage-backend","heading":"First-party event logging exporter takes a storage backend","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/first-party-event-logging-exporter-takes-a-storage-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### First-party event logging exporter takes a storage backend\n\nEvent logging now routes through a cached storage backend.\n\n**What**\n\nThe 1p event-logging initializer now threads a storage backend through to the log exporter.\n\n**Details**\n\n- the backend is cached in a module-level slot on first call\n- passed to the exporter as `storageV5` alongside baseUrl, path and the kill switch\n- the overall storageV5 surface grew from 24 to 27 references between builds\n\n**Evidence**\n\n`storageV5`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}