We have an Azure AppService, hosting a classic ASP.NET application. We're noticing that the D:\home\LogFiles folder on the AppService has many hundreds of log files named SnapshotUploader64_ABCDEF.log where ABCDEF is 6 alphanumeric characters. Many of these files are close to 100KB.
What are these files? Why are there so very many, potentially filling up our Log space.
Each log file seems to be a trace of AppInsights PDP inspection, mini-dump writing and snapshot uploads. Can this trace be turned off?
When we surf to the Kudu SCM DebugConsole page we see a long list of error messages in the Kudu console --
There are xxx items in this directory, but maxViewItems is set to 299. You can increase maxViewItems by setting it to a larger value in localStorage.
If they can't be turned off, can we have them put elsewhere, such as below the LogFiles\ApplicationInsights subfolder?
I'm a developer on Snapshot Collector. Currently users can't change the log path in Azure App Service or specify a lot rotation rule. I've added your feature request in our backlog and we'll probably implement it in the next release. Please follow the release notes.
As a workaround you can open Kudu in D:\home\LogFiles and run "rm SnapshotUploader*.log" to remove the old files. The current one will not be removed because it's locked by the running app.
If the app runs on any other platform them you can change the TempFolder configuration and logs will be written under [TempFolder]\Dumps(64)\[instrumentation key]\