{"version":"2.1.246","anchor":"session-log-rotation-uses-the-storage-backend-when-one-is-pr","canonical_anchor":"session-log-rotation-uses-the-storage-backend-when-one-is-pr","heading":"Session log rotation uses the storage backend when one is present","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/session-log-rotation-uses-the-storage-backend-when-one-is-pr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Session log rotation uses the storage backend when one is present\n\nSession log rotation goes through the storage backend, with a retry if renaming fails.\n\n**What**\n\nChecking log size and rotating a log to its `.1` copy now go through backend stat, rename and delete calls when the storage backend is available, with a delete-then-retry if the rename fails. Without it, the previous filesystem path runs unchanged.\n\n**Evidence**\n\n`this.storageV5.hostFiles`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}