Open j82w opened 2 years ago
Example of the diagnostics missing entries. Notice it's still being collected at 10 second interval, but some are missing. This points to a possible bug that is getting only logged to traces. It should be added to the diagnostics so the problem can be root caused and fixed.
"System Info": {
"systemHistory": [
{
"dateUtc": "2022-05-25T12:02:17.7081784Z",
"cpu": 4.253,
"memory": 5034956.000,
"threadInfo": {
"isThreadStarving": "False",
"threadWaitIntervalInMs": 0.3737,
"availableThreads": 32766,
"minThreads": 2,
"maxThreads": 32767
}
},
{
"dateUtc": "2022-05-25T12:02:37.7050251Z",
"cpu": 4.808,
"memory": 5035208.000,
"threadInfo": {
"isThreadStarving": "False",
"threadWaitIntervalInMs": 0.2534,
"availableThreads": 32766,
"minThreads": 2,
"maxThreads": 32767
}
},
{
"dateUtc": "2022-05-25T12:02:57.7051946Z",
"cpu": 4.394,
"memory": 5035588.000,
"threadInfo": {
"isThreadStarving": "False",
"threadWaitIntervalInMs": 0.0203,
"availableThreads": 32766,
"minThreads": 2,
"maxThreads": 32767
}
},
{
"dateUtc": "2022-05-25T12:03:07.7095160Z",
"cpu": 5.220,
"memory": 5035444.000,
"threadInfo": {
"isThreadStarving": "False",
"threadWaitIntervalInMs": 0.3052,
"availableThreads": 32766,
"minThreads": 2,
"maxThreads": 32767
}
},
{
"dateUtc": "2022-05-25T12:03:17.7124857Z",
"cpu": 3.497,
"memory": 5034220.000,
"threadInfo": {
"isThreadStarving": "False",
"threadWaitIntervalInMs": 0.0296,
"availableThreads": 32766,
"minThreads": 2,
"maxThreads": 32767
}
},
There has been several instance where the diagnostics does not have the CPU history, and in some scenarios it's missing entries. The history is every 10 seconds, but then one is missing.
To understand why the CPU is not collected the exception message should be logged to the diagnostics to help troubleshoot this issue.
https://msdata.visualstudio.com/_git/CosmosDB?path=/Product/Microsoft.Azure.Documents/SharedFiles/Rntbd2/SystemUsageMonitor.cs
Example part of the diagnostics where it is missing:
With the change the JSON should look something like: