Are you using Microsoft SQL Server in your application? You can use CopperEgg to monitor your Microsoft SQL Server performance. As an illustration, you can configure and receive alerts for the following scenarios:
- Performance: alert if the Microsoft SQL Server performance is poor.
- If the cpu_usage value is significantly above its normal range, that would imply that the Microsoft SQL Server is under heavy load.
CopperEgg offers a SAAS based out-of-the-box solution for monitoring Microsoft SQL Server for performance and availability. If you are not familiar with the concept of custom metrics as used in CopperEgg, please go through Custom Metrics information once before continuing with this document.
- CopperEgg account.
If you don’t already have an account, you can sign up for a 14 day FREE TRIAL of CopperEgg. (no Credit Card required).
- Microsoft SQL Server up and running in your environment.
- Root access to server to install the Microsoft SQL Server agent.
Monitor Microsoft SQL Server using out-of-the-box custom metrics installer from CopperEgg
There are three steps that you need to do to start monitoring a Microsoft SQL Server:
- Microsoft SQL Server Agent Installation
- Verify that your Microsoft SQL Server Dashboard is up and running
- Configure alerts to be notified about Microsoft SQL Server performance issues
1.Microsoft SQL Server Agent Installation
Figure 1: In your CopperEgg Account, navigate to Databases>Getting Started
Login to your CopperEgg account and navigate to Custom tab -> Getting Started. Click on Microsoft SQL Server icon. .
Figure 2: The Microsoft SQL Server agent installation script
Click on icon to copy the installer script to your clipboard. Paste the command into the terminal window on the server where you want to install the agent. Script can be run on the server running Microsoft SQL Server, or it can be a different server, but this server will need to be continually running in order to monitor Microsoft SQL Server.
As soon as the script is run on a terminal with root access, it starts downloading the required Microsoft SQL Server monitoring agent on your server. You will need to configure the following items in the agent installation process. Item specified in square brackets ( [ ] ) are the default.
Figure 3: Executing the Microsoft SQL Server agent installation script
- Press y to monitor Microsoft SQL Server.
Figure 4: Executing the Microsoft SQL Server agent installation script with monitoring frequency as 60 seconds
- Monitoring frequency: 15, , 300, 900, 3600 seconds
Figure 5: Executing the Microsoft SQL Server agent installation script with group name as “MSSQL”, group label as “SQL Server Metrics” and Dashboard as “SQL Server”
- Group label, group name and dashboard name for custom metrics [MSSQL][SQL Server Metrics][SQL Server]
Figure 6: Executing the Microsoft SQL Server agent installation script with unique name, authentication type, server hostname , username, password. Only one Microsoft SQL Server is added for monitoring.
- Unique name for this server (good to differentiate if you are monitoring different Microsoft SQL Servers). [instance1 is default]
- Server Name
- Authentication type, hostname username,password(for sql authentication). We are choosing Windows Authentication mode in this illustration.
- After configuring one database, you’ll get an option to add more Microsoft SQL Servers.
Figure 7: Executing the Microsoft SQL Server agent installation script with an upstart init file and the default value for log file name. The installation completes successfully!
- Configure Microsoft Azure SQL Server[Default : N]
2.Verify that your Microsoft SQL Server Dashboard is up and running
Navigate to Dashboard and you will see a new Microsoft SQL Server Dashboard has been added automatically by the installer.
Figure 8: A new Dashboard for Microsoft SQL Server has been added
As the installed script executes, you will notice data samples appearing on the widgets for this Dashboard.
Figure 9: Widget inside Microsoft SQL Server Dashboard displaying cache hits ratio.
Figure 10: Widget inside Microsoft SQL Server Dashboard displaying batch requests per second.
Figure 11: Widget inside Microsoft SQL Server Dashboard displaying checkpoint pages per second.
CopperEgg currently monitors 29 metrics which cover most of the important metrics for Microsoft SQL Server from a performance and stability perspective. You can see these 29 metrics by navigating to the Custom Tab > Custom Objects and selecting Details on the Custom Metrics Group Label [SQL Server Metrics] that was given as installation input. For some of these metrics, alerts have been automatically created (see section 3 below). To create new alerts see section: Configuring your own Alerts for the Microsoft SQL Server Database.
The metrics are:
- active_parallel_threads : Active Parallel Threads (alert automatically created)
- active_requests : Active Requests (alert automatically created)
- active_transactions : Active Transactions (alert automatically created)
- backup_restore_throughput_sec : Backup Restore Throughput/Sec
- batch_requests_sec : Batch Requests/Sec
- blocked_tasks : Blocked Tasks
- cache_hit_ratio : Cache Hit Ratio
- cache_object_counts : Cache Object Counts
- checkpoint_pages_sec : Checkpoint Pages/Sec
- cpu_usage : CPU Usage (%) (alert automatically created)
- dropped_messages_total : Dropped Messages Total
- errors_sec : Errors/Sec
- free_memory : Free Memory (alert automatically created)
- lock_wait : Lock Wait
- number_of_deadlocks_sec : No. of Deadlocks/Sec (alert automatically created)
- open_connection_count : Open Connections Count (alert automatically created)
- page_life_expectancy : Page Life Expectancy
- page_lookups_sec : Page Lookups/Sec
- page_reads_sec : Page Reads/Sec
- page_splits_sec : Access Page Splits
- page_writes_sec : Page Writes/Sec
- processes_blocked : Processes Blocked (alert automatically created)
- queued_requests : Queued Requests
- sql_compilations_sec : SQL Compilations/Sec
- sql_re_compilations_sec : SQL Recompilations/Sec
- transaction_delay : Transaction Delay
- transaction_ownership_waits : Transaction Ownership Waits
- transactions : Transactions
- write_transactions_sec : Write Transactions/Sec
3.Configure Alerts to be notified about Microsoft SQL Server performance issues.
Default Pre-Configured Alerts for the Microsoft SQL Server Database
As soon as your Microsoft SQL Server Database Monitoring Dashboard comes up, you will notice that some alert configurations have been automatically created by our Installation Script (under Alerts > Configure Alerts). These pre-configured alerts for Microsoft SQL Server Database include:
|Active Parallel threads
|Current number of active Parallel threads
|Current number of active requests
|Current number of active transactions
|Average CPU utilization
|Number of deadlocks
|Count of deadlocks
|Alert when Number of Deadlocks greater than or equal to 1.
|Open connection count
|Count of open connections
|Count of blocked processes
|Alert when processes blocked greater than or equal to 1.
If the alerting condition is met for these pre-configured alerts, some alert notifications may also be triggered.
Configuring your own Alerts for the Microsoft SQL Server Database
Figure 12: A new alert being added that will be triggered when cpu usage metric exceeds a threshold of <entered value> within a time period of 1 min
Alerts can also be configured against any of these 29 monitored metrics for Microsoft SQL Server.
You can configure new alerts that will be triggered when performance issues with Microsoft SQL Server arise. You can also configure the notification mechanisms for a triggered alert.
- Go to Alerts Tab > Configure alerts and click on “New Alerts” button
- Provide values for these fields in the New Alert page:
- Description: A description of the alert that will be easily recognized by you and your team if the alert is triggered
- Alert me when: Select the metric of interest and the condition upon which the alert is triggered. In the Alert me when dropdown, you can prefill “Custom: <your Microsoft SQL Server Metric Group>” to get only the list of monitored metrics for your specific Microsoft SQL Server. From this list, you can then select the specific metric for which you want to configure an alert. As an illustration, in Figure 12, the chosen metric of interest in ‘Alert me when’ is ‘Custom: SQL Server Metrics: CPU Usage(%)’ and the condition for triggering the alert is if the average value is more than <entered value in dropdown>.
- For at least: The duration for which the alert condition must be valid for the alert to be triggered
- Matching tags: By default, (match everything) is chosen. If needed, you can attach tags to a particular metric object and select those tags here, which would cause only alerts on that metric object to be triggered.
- Excluding tags: By default, (exclude nothing) is chosen. If needed, you can attach tags to a particular metric object and select those tags here, which would cause alerts on that metric object to be skipped.
- Annotate: When enabled, an annotation is automatically created when the alert is triggered. Annotations will be visible in the custom metrics dashboard where the data stream is displayed.
- Automatic Clear: When enabled, the alert issue is automatically cleared if the triggering condition is no longer true
- Notify on clear: When enabled, notifications are also sent when the alert issue is cleared. Please do note that notifications are always sent when the alert issue is triggered.
- Send Notifications To: Here you can configure the notification mechanisms by which the alert is communicated to you and others in your team.
CopperEgg supports notifying different sets of users with differing notification mechanisms for each alert type.
Notification mechanisms include:
Webhooks are also exposed for clients to configure custom notification mechanisms.
More about setting up website probe alerts can be found here.
CopperEgg Free Trial! Sign up today!
You can find more information about CopperEgg pricing options here.
We charge only $0.08 per month per metric!
Sign up today!