We are not sure why this happens, but restarting the SQL Server service and then the SQL Monitor Base Monitor service seems to clear it up. This has worked for users who have reported this previously, but please let me know if it does not work for you.
Thank you for your reply.
There is no issue at all with monitoring the SQL Server instance which hosts the RedGateMonitor database.
Which "monitor service" have you restarted? The "SQL Monitor 3 Base Monitor" service is the important one here.
Tips and how-to guides for Redgate products
Ask, discuss, and solve questions about Redgate's tools
Meet us at an event, get sponsored, and join our Friends of Redgate
In-depth articles and opinion from Redgate's technical journal