Comments
1 comment
-
I believe that when the Base Monitor service re-establishes contact with a monitored entity it will run some quick data connection tests to ensure that it has contact. However, the spikes that you describe do sound out of the ordinary.
Would it be possible for you to send me the SQL Monitor error logs, as described in this document, by emailing support@red-gate.com and quote the ticket number F0060280 in the subject line:
http://www.red-gate.com/supportcenter/c ... M_LogFiles
Add comment
Please sign in to leave a comment.
After a looking at a few things we realised the PC where we run SQL Monitor on had been rebooted a few times. These reboots seems to correspond with the CPU spikes.
So we tested it by rebooting SQL Monitor again and sure enough it case the CPU spikes on all monitored servers.
These spikes don't last very long but they do reach close to 100% (maxing out on some occasions)