Hello @Mavi ,
After detailed investigation, we’ve identified the following contributing factors to the app restarts and downtime for brandiving:
Azure File System Path Change:
The message “File server volume path change” indicates that Azure has changed the underlying network-mounted storage path—typically triggered by platform maintenance or latency. When this happens, Azure reboots the app to remount the new file system path.
Low Swap Space:
Our monitoring tools show that brandiving experienced swap space dropping below 800MB. Low swap availability, especially under memory pressure, can lead to instability and app restarts.
The swap usage per process can be estimated with:
SWAP = VIRT - RES.
Auto-Heal Not Enabled:
Auto-Heal is not currently enabled on the app. Enabling this can help proactively restart the app when it encounters high memory usage, specific HTTP errors, or slow responses.
Recommendations:
• Monitor swap usage using Linux memory tools or Azure diagnostics.
• Consider scaling to a higher SKU if memory demands are consistently high.
• Enable Auto-Heal with custom rules if needed.
• Use the Diagnose and Solve Problems tool for memory and restart analysis: Diagnose App Restart Issues
For more details refer this App Services on Linux Rebooting due to Memory Limits link
Please don’t forget to click "Accept the answer" and click "Yes" .So it can be helpful for others with similar questions.
If you have any more questions or need clarification, feel free to click Comment.