{"version":"2.1.232","anchor":"event-logging-keeps-its-storage-handle-per-host","canonical_anchor":"event-logging-keeps-its-storage-handle-per-host","heading":"Event logging keeps its storage handle per host","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/event-logging-keeps-its-storage-handle-per-host","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Event logging keeps its storage handle per host\n\nEvent log exports use the storage belonging to that session rather than a shared global.\n\n**What**\n\nThe first-party event logger moved its provider and a storage handle off module-level globals and onto the per-host record, so exporting logs uses the storage backend belonging to that session. Logging still requires the existing first-party logging check.\n\n**Evidence**\n\n`retainedStorageV5`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}