azure / daas Goto Github PK

This is the source code repository for the Diagnostics As A Service component of Azure App Service

License: MIT License

C# 77.22% CSS 3.34% HTML 8.54% JavaScript 9.04% Perl 0.03% PowerShell 1.77% ASP.NET 0.01% Batchfile 0.05%

daas's Introduction

⛔️ DEPRECATED

This project has been migrated over into an internal repository. While we may not be tracking or accepting new issues here in this repo, please feel free to use our feedback channel in our Diagnose and Solve blade in Azure Portal

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Running DaaS as a Private Site Extension

You can build this project locally and install it as a Private Site extension on your Azure App by following these steps.

In Visual Studio, make sure you set the nuget package source to: https://api.nuget.org/v3/index.json
Increment the AssemblyFileVersion and AssemblyVersion inside DaaS\DaaS\Properties\AssemblyInfo.cs and DaaS\DaaSRunner\Properties\AssemblyInfo.cs. They should be higher than this repository's version and they should be exactly the same in both these files.
Make sure that the Release configuration from Visual Studio is chosen. Then, rebuild the whole project and right click on the DiagnosticsExtension project and choose Publish and Publish the FolderProfile.
Take the published content and drag and drop it to d:\home\SiteExtensions\DAAS folder via Kudu Console. (you may have to create the folder first).
Restart the site via Azure Portal to ensure that the app points to DAAS private extension bits.
Now DAAS Extension bits should be pointing to Private Site Extensions folder (d:\home\SiteExtensions\DAAS). To validate, you can browse to https://<yoursitename>.scm.azurewebsites.net/DaaS/api/v2/daasversion and you should see the version that you specified in Step 1.

daas's People

Contributors

Stargazers

Watchers

Forkers

isabella232 madhura0110 clubspark-devops mitikov gajibillik puneetg1983 cablooshe patelchandni hirofuk-ops superchensss richardsonjf sourcecodecheck

daas's Issues

Running DaasConsole.exe for Memory Dumps will fail if BlobSasUri is not specified

Due to recent changes in DaaS and Azure App Service code, if a memory dump session is submitted via DaaSconsole.exe without specifying BlobSasUri switch, the session will not be submitted.

This will be fixed with DaaS version 1.45

Analysis report fails for .NET core memory dumps

The Dump Analysis report may fail to display managed callstacks and other .net analysis information if both .NET Core and .NET Framework are loaded in the process. The analysis report may contain an error like below.

Analysis results may be incomplete because an error occurred while initializing the CLR diagnostic runtime for instance_w3wp_17740.dmp. Dump File: instance_w3wp_17740.dmp Type: DebugDiag.DotNet.DacNotFoundException Message: CLR is loaded in the target, but the correct dac file cannot be found. DacFileName: mscordacwks_Amd64_Amd64_4.8.4210.00.dll. DacLocation:	To fix this problem, you can copy mscordacwks.dll from the server where the dump was taken and rename it to and add the path of the folder to the Symbol server path by going to Tools-> Options and Settings For more details on this issue, please refer to this blog. The following symbol probe information may be helpful: Created SymbolReader with SymbolPath srvf:\nofolderexistshttp://msdl.microsoft.com/download/symbols Probe of http://msdl.microsoft.com/download/symbols/mscordacwks_Amd64_Amd64_4.8.4210.00.dll/5efa67efac1000/mscordacwks_Amd64_Amd64_4.8.4210.00.dll failed: Could not find a part of the path 'f:\nofolderexists\mscordacwks_Amd64_Amd64_4.8.4210.00.dll\5efa67efac1000'. Probe of http://msdl.microsoft.com/download/symbols/mscordacwks_Amd64_Amd64_4.8.4210.00.dll/5efa67efac1000/mscordacwks_Amd64_Amd64_4.8.4210.00.dl_ failed: The remote server returned an error: (404) Not Found. Probe of http://msdl.microsoft.com/download/symbols/mscordacwks_Amd64_Amd64_4.8.4210.00.dll/5efa67efac1000/file.ptr failed: The remote server returned an error: (404) Not Found.

This issue will be fixed with ANT 92.

Choosing an existing Storage Account may fail with the error "The remote server returned an error: (400) Bad Request"

Additional Details

While trying to use an existing storage account, the SAS key generation failing with the error “The remote server returned an error: (400) Bad Request.” This issue happens when someone chooses "StorageV2 (general purpose v2)" storage account and it appears that endpoints for V2 storage accounts accept calls over TLS 1.2 protocol only.

This issue will be addressed in DaaS version 1.43 where in all the DaaS code will force all the outbound calls over TLS 1.2 protocol only. Once DaaS Version 1.43 is available everywhere in Azure App Service, this issue will be closed.

Memory Dump Collector may fail with Disk Full errors

Memory Dump collector is currently checking disk space of D:\HOME where as memory dumps are not copied to D:\HOME at all so the check is incorrect and should be removed.

Temp files created by CLR Profiler are not deleted sometimes

Uncompressing C:\local\Temp\Logs\xxxxxxx\xxxxxxxxxxxxx\xxxxxxxxxxx.diagsession to C:\local\Temp\ETL.xxxxxxxxxxxxxx...
Failed to extract files due to this exception:

Failed while extracting ETL Trace. LocalFilePath is C:\local\Temp\Logs\xxxxxxxxxxxxxxxxxx_w3wp_5144_20220718-190155.diagsession_sc.user_aux.etl and Disk Usage Details are  C:\local has totalBytes = [150323855360]  and freeBytes = [125559492608] and UsedPercent = 16 , C:\home has totalBytes = [268435456000]  and freeBytes = [266105233408] and UsedPercent = 1  and Exception System.Runtime.InteropServices.COMException:There is not enough space on the disk. (Exception from HRESULT: 0x80070070)

    at DiagnosticsHub.Packaging.Interop.IDhPackage.ExtractResourceToPath(Guid& ResourceId, String extractionPath)

   at Microsoft.DiagnosticsHub.Packaging.InteropEx.DhPackageNative.ExtractResourceToPath(Guid& resourceId, String extractionPath)

   at ClrProfilingAnalyzer.Program.GetLocalFilePath(String packageFilePath, DhPackage package, ResourceInfo resource, String fileExtension)

TLS errors logged at Web App startup

Sorry if this is the incorrect place but I recently required TLS 1.2 on my storage accounts and this has lead to some TLS errors being logged to my Kudu instance. This is occurring for multiple apps running on a Windows App Service plan using .NET 4.8 and to multiple storage accounts. My apps are all able to r/w to these storage accounts without issue. Each app is set to log application logs, web server logs, detailed error messages and failed request traces to blob storage. There are logs going to these storage accounts, I'm just unsure if I'm missing any. The following is what gets logged at app startup:

2022-01-18T12:06:09
Microsoft.WindowsAzure.Storage.StorageException: The remote server returned an error: (400) Bad Request. ---> System.Net.WebException: The remote server returned an error: (400) Bad Request.
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.WindowsAzure.Storage.Core.Executor.Executor.ExecuteSync[T](RESTCommand1 cmd, IRetryPolicy policy, OperationContext operationContext) --- End of inner exception stack trace --- at Microsoft.WindowsAzure.Storage.Core.Executor.Executor.ExecuteSync[T](RESTCommand1 cmd, IRetryPolicy policy, OperationContext operationContext)
at Microsoft.WindowsAzure.Storage.Blob.CloudBlockBlob.DownloadBlockList(BlockListingFilter blockListingFilter, AccessCondition accessCondition, BlobRequestOptions options, OperationContext operationContext)
at Microsoft.WindowsAzure.WebSites.Diagnostics.AzureBlobTraceListener.AppendStreamToBlob(Stream stream)
at Microsoft.WindowsAzure.WebSites.Diagnostics.AzureBlobTraceListener.ConsumeBuffer()
Request Information
RequestID:19a439a8-801e-006d-0363-0c50cf000000
RequestDate:Tue, 18 Jan 2022 12:06:08 GMT
StatusMessage:The TLS version of the connection is not permitted on this storage account.
ErrorCode:TlsVersionNotPermitted

2022-01-18T12:06:09
Microsoft.WindowsAzure.Storage.StorageException: The remote server returned an error: (400) Bad Request. ---> System.Net.WebException: The remote server returned an error: (400) Bad Request.
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.WindowsAzure.Storage.Core.Executor.Executor.ExecuteSync[T](RESTCommand1 cmd, IRetryPolicy policy, OperationContext operationContext) --- End of inner exception stack trace --- at Microsoft.WindowsAzure.Storage.Core.Executor.Executor.ExecuteSync[T](RESTCommand1 cmd, IRetryPolicy policy, OperationContext operationContext)
at Microsoft.WindowsAzure.Storage.Blob.CloudBlobContainer.ListBlobsSegmented(String prefix, Boolean useFlatBlobListing, BlobListingDetails blobListingDetails, Nullable`1 maxResults, BlobContinuationToken currentToken, BlobRequestOptions options, OperationContext operationContext)
at Microsoft.WindowsAzure.WebSites.Diagnostics.AzureBlobTraceListener.CleanupOldBlobLogs(Object state)
Request Information
RequestID:1dfd4168-601e-0081-3b63-0c445e000000
RequestDate:Tue, 18 Jan 2022 12:06:08 GMT
StatusMessage:The TLS version of the connection is not permitted on this storage account.
ErrorCode:TlsVersionNotPermitted

2022-01-18T12:06:09
Microsoft.WindowsAzure.Storage.StorageException: The remote server returned an error: (400) Bad Request. ---> System.Net.WebException: The remote server returned an error: (400) Bad Request.
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.WindowsAzure.Storage.Core.Executor.Executor.ExecuteSync[T](RESTCommand1 cmd, IRetryPolicy policy, OperationContext operationContext) --- End of inner exception stack trace --- at Microsoft.WindowsAzure.Storage.Core.Executor.Executor.ExecuteSync[T](RESTCommand1 cmd, IRetryPolicy policy, OperationContext operationContext)
at Microsoft.WindowsAzure.Storage.Blob.CloudBlockBlob.DownloadBlockList(BlockListingFilter blockListingFilter, AccessCondition accessCondition, BlobRequestOptions options, OperationContext operationContext)
at Microsoft.WindowsAzure.WebSites.Diagnostics.AzureBlobTraceListener.AppendStreamToBlob(Stream stream)
at Microsoft.WindowsAzure.WebSites.Diagnostics.AzureBlobTraceListener.ConsumeBuffer()
Request Information
RequestID:051c05da-d01e-0060-5863-0c981b000000
RequestDate:Tue, 18 Jan 2022 12:06:09 GMT
StatusMessage:The TLS version of the connection is not permitted on this storage account.
ErrorCode:TlsVersionNotPermitted

Standard Azure support has proven unhelpful so I'm wondering if there is some configuration I'm missing.

DaaS CollectKillAnalyze in Azure app service as auto-heal 'FATAL Error :ProcDump failed to run.'

I've setup a custom Auto-Heal configuration in my Azure app service which performs a CollectKillAnalyze when a memory-condition meets certain threshold. The condition were meets so the auto-heal action was executed but the memory dump is not created.

MemoryDumpCollector.exe Information: 0 : 10/13/2021 8:28:33 AM [[1.56]] [pd1mdwk000020] statusFilePath = c:\home\data\daas\logs\(...)\211013_0828056155\pd1mdwk000020\memorydumpcollector
MemoryDumpCollector.exe Error: 0 : 10/13/2021 8:28:39 AM MemoryDumpCollector: FATAL Error :ProcDump failed to run. Detailed ProcDump output: 
 [08:28:36] Dump 1 error: Error writing dump file: 0x80070006
The handle is invalid. (0x80070006, -2147024890)  
MemoryDumpCollector.exe Information: 0 : 10/13/2021 8:29:19 AM [[1.56]] [pd1mdwk000020] statusFilePath = c:\home\data\daas\logs\(...)\211013_0828056155\pd1mdwk000020\memorydumpcollector
MemoryDumpCollector.exe Error: 0 : 10/13/2021 8:29:21 AM MemoryDumpCollector: FATAL Error :ProcDump failed to run. Detailed ProcDump output: 
 [08:29:19] Dump 1 error: Error writing dump file: 0x80070006
The handle is invalid. (0x80070006, -2147024890)  
MemoryDumpCollector.exe Information: 0 : 10/13/2021 8:29:57 AM [[1.56]] [pd1mdwk000020] statusFilePath = c:\home\data\daas\logs\(...)\211013_0828056155\pd1mdwk000020\memorydumpcollector
MemoryDumpCollector.exe Error: 0 : 10/13/2021 8:30:00 AM MemoryDumpCollector: FATAL Error :ProcDump failed to run. Detailed ProcDump output: 
 [08:29:58] Dump 1 error: Error writing dump file: 0x80070006
The handle is invalid. (0x80070006, -2147024890)  
MemoryDumpCollector.exe Information: 0 : 10/13/2021 8:30:35 AM [[1.56]] [pd1mdwk000020] statusFilePath = c:\home\data\daas\logs\(...)\211013_0828056155\pd1mdwk000020\memorydumpcollector
MemoryDumpCollector.exe Error: 0 : 10/13/2021 8:30:37 AM MemoryDumpCollector: FATAL Error :ProcDump failed to run. Detailed ProcDump output: 
 [08:30:36] Dump 1 error: Error writing dump file: 0x80070006
The handle is invalid. (0x80070006, -2147024890)  
MemoryDumpCollector.exe Information: 0 : 10/13/2021 8:31:13 AM [[1.56]] [pd1mdwk000020] statusFilePath = c:\home\data\daas\logs\(...)\211013_0828056155\pd1mdwk000020\memorydumpcollector
MemoryDumpCollector.exe Error: 0 : 10/13/2021 8:31:17 AM MemoryDumpCollector: FATAL Error :ProcDump failed to run. Detailed ProcDump output: 
 [08:31:15] Dump 1 error: Error writing dump file: 0x80070006
The handle is invalid. (0x80070006, -2147024890)  
MemoryDumpCollector.exe Information: 0 : 10/13/2021 8:31:51 AM [[1.56]] [pd1mdwk000020] statusFilePath = c:\home\data\daas\logs\(...)\211013_0828056155\pd1mdwk000020\memorydumpcollector
MemoryDumpCollector.exe Error: 0 : 10/13/2021 8:31:54 AM MemoryDumpCollector: FATAL Error :ProcDump failed to run. Detailed ProcDump output: 
 [08:31:52] Dump 1 error: Error writing dump file: 0x80070006
The handle is invalid. (0x80070006, -2147024890)  
MemoryDumpCollector.exe Information: 0 : 10/13/2021 8:32:30 AM [[1.56]] [pd1mdwk000020] statusFilePath = c:\home\data\daas\logs\(...)\211013_0828056155\pd1mdwk000020\memorydumpcollector
MemoryDumpCollector.exe Error: 0 : 10/13/2021 8:32:32 AM MemoryDumpCollector: FATAL Error :ProcDump failed to run. Detailed ProcDump output: 
 [08:32:31] Dump 1 error: Error writing dump file: 0x80070006
The handle is invalid. (0x80070006, -2147024890)

I thought I set the Auto-Heal custom action to write the memory dump to a blob storage, but it wasn't. Could it be insufficient disk space to write the memory dump?

Elastic Premium function app - Proactive CPU Monitoring

In EP function apps, the proactive CPU Monitoring feature is not available because "Always On" feature is not enabled.

Since Always On feature is not available in EP plans, Proactive CPU monitoring should be available to troubleshoot CPU related issues.

If it is not possible to enable the feature, the message should be changed, as it would confuse customers because there is not Always On option to enable. And an alternative should be available to collect memory dumps and/or mitigate CPU issues by restarting the issue automatically.

Error during memory dump collector ':ProcDump failed to run'

For sites with long site names, creating a profiler trace may fail with PathTooLongException

An issue was reported for sites that have a long name where creation a profiler trace will fail in the Portal with PathTooLongException.

Workaround

Please use the Collect Profiler Trace option by going to the KUDU console for the app. Also make sure that the "Collect IIS Events" option is selected to ensure that all the right events are captured

This will be fixed in DAAS 1.53 update.

Could not load file or assembly 'Newtonsoft.Json, Version=13.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.

Unable to collect a memory dump because DaaS is not running DaaS is not running because it can't find Newtonsoft.Json. Should this dependency be deployed with DaaS to my Azure Function App?

[01/18/2024 23:06:12 > a66d27: SYS INFO] Detected WebJob file/s were updated, refreshing WebJob
[01/18/2024 23:06:12 > a66d27: SYS INFO] Status changed to Starting
[01/18/2024 23:06:12 > a66d27: SYS INFO] WebJob singleton setting is False
[01/18/2024 23:06:13 > a66d27: SYS INFO] Run script 'DaasRunner.exe' with script host - 'WindowsScriptHost'
[01/18/2024 23:06:13 > a66d27: SYS INFO] Status changed to Running
[01/18/2024 23:09:21 > a66d27: SYS INFO] WebJob is stopping due to website shutting down
[01/18/2024 23:09:21 > a66d27: SYS INFO] Status changed to Stopping
[01/18/2024 23:09:26 > a66d27: ERR ] Thread was being aborted.
[01/18/2024 23:09:26 > a66d27: SYS INFO] WebJob process was aborted
[01/18/2024 23:09:26 > a66d27: SYS INFO] Status changed to Stopped
[01/18/2024 23:09:34 > a66d27: SYS INFO] Status changed to Starting
[01/18/2024 23:09:34 > a66d27: SYS INFO] WebJob singleton setting is False
[01/18/2024 23:09:34 > a66d27: SYS INFO] Run script 'DaasRunner.exe' with script host - 'WindowsScriptHost'
[01/18/2024 23:09:35 > a66d27: SYS INFO] Status changed to Running
[01/19/2024 00:09:34 > a66d27: SYS INFO] WebJob is still running
[01/19/2024 12:09:34 > a66d27: SYS INFO] WebJob is still running
[01/19/2024 14:26:21 > a66d27: INFO] Including any child processes
[01/19/2024 14:26:21 > a66d27: INFO] Will take dump of following processes:
[01/19/2024 14:26:21 > a66d27: INFO]   w3wp - Id: 14676
[01/19/2024 14:26:21 > a66d27: INFO] w3wp is 64-bit
[01/19/2024 14:26:21 > a66d27: INFO] Comand:
[01/19/2024 14:26:22 > a66d27: INFO] C:\Program Files (x86)\SiteExtensions\DaaS\3.9.23829.01\bin\DiagnosticTools\procdump.exe  -accepteula -r -dc "InvokedViaDaasConsole-Memory" -ma 14676 C:\local\Temp\Logs\240119_1425553170\aw0sdwk0000CQ\aw0sdwk0000CQ_w3wp_14676_20240119-142621.dmp
[01/19/2024 14:27:58 > a66d27: ERR ] 
[01/19/2024 14:27:58 > a66d27: ERR ] Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Newtonsoft.Json, Version=13.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.
[01/19/2024 14:27:58 > a66d27: ERR ]    at StackTracer.Program.Main(String[] args)
[01/19/2024 14:33:18 > 9a92f1: SYS INFO] Status changed to Starting
[01/19/2024 14:33:18 > 9a92f1: SYS INFO] WebJob singleton setting is False
[01/19/2024 14:33:18 > 9a92f1: SYS INFO] Run script 'DaasRunner.exe' with script host - 'WindowsScriptHost'
[01/19/2024 14:33:18 > 9a92f1: SYS INFO] Status changed to Running
[01/19/2024 14:38:19 > a66d27: INFO] Including any child processes
[01/19/2024 14:38:19 > a66d27: INFO] Will take dump of following processes:
[01/19/2024 14:38:19 > a66d27: INFO]   w3wp - Id: 12892
[01/19/2024 14:38:19 > a66d27: INFO] w3wp is 64-bit
[01/19/2024 14:38:19 > a66d27: INFO] Comand:
[01/19/2024 14:38:19 > a66d27: INFO] C:\Program Files (x86)\SiteExtensions\DaaS\3.9.23829.01\bin\DiagnosticTools\procdump.exe  -accepteula -r -dc "InvokedViaDaasConsole-Memory" -ma 12892 C:\local\Temp\Logs\240119_1438038193\aw0sdwk0000CQ\aw0sdwk0000CQ_w3wp_12892_20240119-143819.dmp
[01/19/2024 14:45:33 > a66d27: SYS INFO] WebJob is stopping due to website shutting down
[01/19/2024 14:45:33 > a66d27: SYS INFO] Status changed to Stopping
[01/19/2024 14:45:38 > a66d27: ERR ] Thread was being aborted.
[01/19/2024 14:45:39 > a66d27: SYS INFO] WebJob process was aborted
[01/19/2024 14:45:39 > a66d27: SYS INFO] Status changed to Stopped
[01/19/2024 15:33:18 > 9a92f1: SYS INFO] WebJob is still running
[01/19/2024 15:34:54 > c0a474: SYS INFO] Status changed to Starting
[01/19/2024 15:34:56 > c0a474: SYS INFO] WebJob singleton setting is False
[01/19/2024 15:34:57 > c0a474: SYS INFO] Run script 'DaasRunner.exe' with script host - 'WindowsScriptHost'
[01/19/2024 15:34:57 > c0a474: SYS INFO] Status changed to Running
[01/19/2024 15:43:37 > 9a92f1: INFO] Including any child processes
[01/19/2024 15:43:37 > 9a92f1: INFO] Will take dump of following processes:
[01/19/2024 15:43:37 > 9a92f1: INFO]   w3wp - Id: 5116
[01/19/2024 15:43:37 > 9a92f1: INFO] w3wp is 64-bit
[01/19/2024 15:43:37 > 9a92f1: INFO] Comand:
[01/19/2024 15:43:37 > 9a92f1: INFO] C:\Program Files (x86)\SiteExtensions\DaaS\3.9.23829.01\bin\DiagnosticTools\procdump.exe  -accepteula -r -dc "InvokedViaDaasConsole-Memory" -ma 5116 C:\local\Temp\Logs\240119_1543286414\aw0sdwk0000CR\aw0sdwk0000CR_w3wp_5116_20240119-154337.dmp
[01/19/2024 15:47:03 > 9a92f1: SYS INFO] WebJob is stopping due to website shutting down
[01/19/2024 15:47:03 > 9a92f1: SYS INFO] Status changed to Stopping
[01/19/2024 15:47:08 > 9a92f1: ERR ] Thread was being aborted.
[01/19/2024 15:47:08 > 9a92f1: SYS INFO] WebJob process was aborted
[01/19/2024 15:47:08 > 9a92f1: SYS INFO] Status changed to Stopped
[01/19/2024 16:34:57 > c0a474: SYS INFO] WebJob is still running
[01/19/2024 17:03:39 > c0a474: SYS INFO] WebJob is stopping due to website shutting down
[01/19/2024 17:03:39 > c0a474: SYS INFO] Status changed to Stopping
[01/19/2024 17:03:44 > c0a474: ERR ] Thread was being aborted.
[01/19/2024 17:03:44 > c0a474: SYS INFO] WebJob process was aborted
[01/19/2024 17:03:44 > c0a474: SYS INFO] Status changed to Stopped
[01/19/2024 17:04:02 > c0a474: SYS INFO] Status changed to Starting
[01/19/2024 17:04:02 > c0a474: SYS INFO] WebJob singleton setting is False
[01/19/2024 17:04:03 > c0a474: SYS INFO] Run script 'DaasRunner.exe' with script host - 'WindowsScriptHost'
[01/19/2024 17:04:03 > c0a474: SYS INFO] Status changed to Running
[01/19/2024 17:08:12 > c0a474: SYS INFO] WebJob is stopping due to website shutting down
[01/19/2024 17:08:12 > c0a474: SYS INFO] Status changed to Stopping
[01/19/2024 17:08:17 > c0a474: ERR ] Thread was being aborted.
[01/19/2024 17:08:17 > c0a474: SYS INFO] WebJob process was aborted
[01/19/2024 17:08:17 > c0a474: SYS INFO] Status changed to Stopped
[01/19/2024 17:08:24 > c0a474: SYS INFO] Status changed to Starting
[01/19/2024 17:08:24 > c0a474: SYS INFO] WebJob singleton setting is False
[01/19/2024 17:08:25 > c0a474: SYS INFO] Run script 'DaasRunner.exe' with script host - 'WindowsScriptHost'
[01/19/2024 17:08:25 > c0a474: SYS INFO] Status changed to Running
[01/19/2024 17:47:22 > c0a474: SYS INFO] WebJob is stopping due to website shutting down
[01/19/2024 17:47:22 > c0a474: SYS INFO] Status changed to Stopping
[01/19/2024 17:47:25 > c0a474: SYS INFO] Status changed to Starting
[01/19/2024 17:47:25 > c0a474: SYS INFO] WebJob singleton setting is False
[01/19/2024 17:47:27 > c0a474: SYS WARN] Failed to delete temporary directory
[01/19/2024 17:47:27 > c0a474: ERR ] Thread was being aborted.
[01/19/2024 17:47:27 > c0a474: SYS INFO] Run script 'DaasRunner.exe' with script host - 'WindowsScriptHost'
[01/19/2024 17:47:27 > c0a474: SYS INFO] WebJob process was aborted
[01/19/2024 17:47:27 > c0a474: SYS INFO] Status changed to Running
[01/19/2024 17:47:27 > c0a474: SYS INFO] Status changed to Stopped
[01/19/2024 18:47:25 > c0a474: SYS INFO] WebJob is still running

About changing the setting

In the Wiki, it says that you can change the setting like MaxDiagnosticSessionsToKeep in the PrivateSettings.xml file present under d:\home\data\DaaS folder.

where-to-specify-these-settings-and-what-are-the-default-values-

But as far as I tried, I couldn't change the setting by changing the PrivateSettings".xml" (It didn't work).
I could change the setting by changing the PrivateSettings."json". (It did work)

Could you confirm which file is correct to change the setting at this time?