Bug: Processor Utilization HIGH when stats show 25.7%
PDinCA
Posts: 642 Silver 1
Web: Version: 7.0.10.7569
Base: Version: 7.0.10.7569
HIGH priority Alert emitted. Details are:
Min. utilization: 25.7
Max. utilization: 25.7
Avg. utilization: 25.7
Clearly an utterly bogus alert!
Target is SQL 2016 Developer SP1 CU2 on Win2012R2
Another "alert" on a DIFFERENT box (Enterprise 2014 SP2 CU3 on Win2012R2) was for HIGH:
Min. utilization: 1.6
Max. utilization: 1.6
Avg. utilization: 1.6
This is embarrassing...
Kindly fix this "oops!"
UPDATE - It Is Even Worse
From the Developer box:
Min. utilization: -312.1
Max. utilization: 0.0
Avg. utilization: -312.1
UPDATE 2
After getting a NEW "Blocking process" alert, and on drilling down being told "The underlying data for this alert has been purged." (???), I took a look at the Azure box on which SQM, and only SQM sits. Base Monitor eating 27% CPU. SQL eating 50% or more... Another post in this forum talked about 100% CPU usage and upon nuking SQM all was well! I didn't nuke it - I gave it a swift size 13 up the rear, and restarted both SQM Services. Oh look!!! CPU is down in total to the 10-20% range. Cambridge, you have a problem! (Perhaps this explains the utter lethargy of page loads prior to the swift-kick)
UPDATE 3
With this latest effort, I have no option but to SILENCE the Alert, as it is now just noise.
Min. utilization: 100.0
Max. utilization: 0.0
Avg. utilization: NaN
Base: Version: 7.0.10.7569
HIGH priority Alert emitted. Details are:
Min. utilization: 25.7
Max. utilization: 25.7
Avg. utilization: 25.7
Clearly an utterly bogus alert!
Target is SQL 2016 Developer SP1 CU2 on Win2012R2
Another "alert" on a DIFFERENT box (Enterprise 2014 SP2 CU3 on Win2012R2) was for HIGH:
Min. utilization: 1.6
Max. utilization: 1.6
Avg. utilization: 1.6
This is embarrassing...
Kindly fix this "oops!"
UPDATE - It Is Even Worse
From the Developer box:
Min. utilization: -312.1
Max. utilization: 0.0
Avg. utilization: -312.1
UPDATE 2
After getting a NEW "Blocking process" alert, and on drilling down being told "The underlying data for this alert has been purged." (???), I took a look at the Azure box on which SQM, and only SQM sits. Base Monitor eating 27% CPU. SQL eating 50% or more... Another post in this forum talked about 100% CPU usage and upon nuking SQM all was well! I didn't nuke it - I gave it a swift size 13 up the rear, and restarted both SQM Services. Oh look!!! CPU is down in total to the 10-20% range. Cambridge, you have a problem! (Perhaps this explains the utter lethargy of page loads prior to the swift-kick)
UPDATE 3
With this latest effort, I have no option but to SILENCE the Alert, as it is now just noise.
Min. utilization: 100.0
Max. utilization: 0.0
Avg. utilization: NaN
Jesus Christ: Lunatic, liar or Lord?
Decide wisely...
Decide wisely...
