This article shows you how to quickly get it configured. You can be monitoring your instances in a couple of minutes.
You should already have imported your SQL Server instances into SQL CoPilot. If not, go to Getting Started to find out how to do this.
If you are impatient to get started, you can use the quick setup function. You can always refine things afterwards, but quick setup is a good way to get started.
Go to the Configuration -> Setup Monitoring screen, drop down the Tags list and select one or more tags to monitor - see below:
Click Apply and the tags you selected are associated with all alerts.
You can click on any of the alerts to see the default severity and thresholds that have been used.
You don't need to do anything else. Click the button in the toolbar at top left and the monitoring will start.
If you want to change the severity or thresholds for any alerts or add more tags, read on.
Lets change the severity of the Low Disk Space alert to Critical and add another Warning when free space is below 20%.
Click on the Low Disk Space alert, then click on the row underneath showing the tag, severity and threshold. Change the severity to Critical and click Save.
Now click the Add button at the bottom of the screen. In the dialog select the tag, select a severity of Warning, and change the threshold to 20. Click Add to close the dialog. You have now setup the alert so that a Critical alert is raised when disk space drops below 5% free, but only a warning when it drops below 20%. You can add similar alerts with different thresholds for other tags.
So what happens when the monitoring spots an issue?
Two things happen simultaneously. A popup message shows at the top right of the screen. This disappears after 5 seconds. Also, colored badges appear in the toolbar (one for each severity), with a number showing how many alerts have been raised. Click on a badge to view all the alerts.
There are 2 ways to view the alerts. In the Monitoring menu you have the option of an Alert Dashboard and an Alert List. The dashboard displays all instances, color-coded by severity. The list shows all alerts. Clicking on an alert opens a tab for the instance and takes you to the most relevant screen.
The simple answer is - when they are no longer active!
There is no way currently to clear an alert. Some have a threshold, such as the Failed Job alert, that defines how far back in job history to go, while others, like Database Offline, will be active until the database is no longer offline.
If you get an alert because of a high severity error in the log and it doesn't go away, there are a couple of possible reasons for that. Either the error keeps occurring, or you are not cycling the error log nightly. Both of these need to be looked at.
Start using the monitoring functionality. You will probably think of things that could be improved, or of some alerts you would like added. If so, please contact us. We are always looking for new ideas.