Provide option to make Diagnostic Logging settings sticky to a slot
We make generous use of sticky slot settings. They enable us to swap code without swapping configuration.
Unfortunately for our design, diagnostic logging settings cannot be marked as sticky. Before a swap, our production slot might be logging to a production storage account, and our staging slot might be logging to a staging storage account. After the swap, production is logging to stage, and stage is logging to production. This results in muddy log files where one cannot be certain which slot was responsible for which log entries.
Please provide an option to make diagnostic logging settings sticky to a slot, so that we can count on knowing which application is responsible for writing to which log files.
Thanks for the idea! We are reviewing the information.
Keith Rimington commented