You are here

Azure SQL Hyperscale Monitoring

Requires Opsview Cloud or Opsview Monitor 6
check_circle
Opsview Supported

Host Template: Cloud - Azure - SQL - Hyperscale

This host template is one of 31 developed by Opsview to provide the most comprehensive Azure monitoring in the industry.

Azure SQL Database is a cloud database service from Microsoft. SQL Database provides web-facing database functionality as a utility service where you pay only for what you use. Cloud-based database solutions such as SQL Database provide many benefits such as rapid provisioning, cost-effective scalability, high availability, and reduced management overhead. This Host Template only applies to Azure SQL databases that are under the Hyperscale resource model.

This Host Template includes the following Service Checks:

Service Check Name Description Default Thresholds (Warning, Critical) UOM
Azure - SQL - Hyperscale - Allocated Storage The allocated data storage [Default Timespan = 5mins, Default Check Interval = 5mins] N/A B
Azure - SQL - Hyperscale - Connections The number of successful, failed and blocked connections [Default Timespan = 5mins, Default Check Interval = 5mins] N/A N/A
Azure - SQL - Hyperscale - CPU Usage The CPU usage of the database [Default Timespan = 5mins, Default Check Interval = 5mins] cpu_percent=70,90 %
Azure - SQL - Hyperscale - CPU Used The CPU limit and number of CPUs used [Default Timespan = 60mins, Default Check Interval = 60mins] N/A N/A
Azure - SQL - Hyperscale - Data IO Percent The data IO percentage [Default Timespan = 5mins, Default Check Interval = 5mins] physical_data_read_percent=70,90 %
Azure - SQL - Hyperscale - Deadlocks The number of deadlocks [Default Timespan = 5mins, Default Check Interval = 5mins] N/A N/A
Azure - SQL - Hyperscale - Log IO Percent The log IO percentage [Default Timespan = 5mins, Default Check Interval = 5mins] log_write_percent=70,90 %
Azure - SQL - Hyperscale - Process CPU Usage The CPU usage for the SQL Server process [Default Timespan = 5mins, Default Check Interval = 5mins] sqlserver_process_core_percent=70,90 %
Azure - SQL - Hyperscale - Process Memory Usage The memory usage for the SQL Server process [Default Timespan = 5mins, Default Check Interval = 5mins] sqlserver_process_memory_percent=70,90 %
Azure - SQL - Hyperscale - Sessions Percent The percentage of sessions [Default Timespan = 5mins, Default Check Interval = 5mins] sessions_percent=70,90 %
Azure - SQL - Hyperscale - Tempdb Percent The Tempdb log used percentage [Default Timespan = 5mins, Default Check Interval = 5mins] tempdb_log_used_percent=70,90 %
Azure - SQL - Hyperscale - Tempdb Used The Tempdb data size and log size [Default Timespan = 5mins, Default Check Interval = 5mins] N/A B
Azure - SQL - Hyperscale - Workers Percent The percentage of workers [Default Timespan = 5mins, Default Check Interval = 5mins] workers_percent=70,90 %
Azure - SQL - Hyperscale - XTP Storage Percent The percentage of XTP (in-memory OLTP) storage used [Default Timespan = 5mins, Default Check Interval = 5mins] xtp_storage_percent=70,90 %

NOTE: The "Default Timespan" given for these Service Checks refers to the time period we use when retrieving metrics from Azure.

NOTE: See details about Nagios thresholds here.

Usage Instructions

To use this Host Template you will need to provide access to the subscription you wish to monitor.

Navigate to the Subscriptions section and select your Subscription.

In the Subscription to be monitored, click Access Control (IAM).

Then click the Add button, select the required role and select the application, once for each of the following roles:

  • Reader

Azure Add Subscription Step 1

Azure Add Subscription Step 2

Repeat these steps for each subscription you wish to monitor.

Note:

Unlike in other Azure Host Templates, the Resource Name field (Arg2) of the AZURE_RESOURCE_DETAILS variable should be set to the name of the SQL server while the SQL Database Name field (Arg1) of the AZURE_SQL_DATABASE_DETAILS variable should be set to the name of the SQL Database (See 'Step 2: Add and configure variables...' below for further details).

Variable Azure Resource Details

Here the SQL Server name is shown in blue while the SQL Database name is shown in red.

Step 1: Add this Host Template

Add the Cloud - Azure - SQL - Hyperscale Host Template to your Opsview Monitor host. If the resource you're monitoring has no hostname or public IP, then open the Advanced settings pane and change Host Check Command to Always assumed to be UP.

For more information, refer to Opsview Knowledge Center - Adding Host Templates to Hosts.

Step 2: Add and configure variables required for this Host Template

The Service Checks in this Host Template use the following variables, and they will be added to your Opsview Monitor instance when you import the Opspack:

AZURE_CREDENTIALS

The Value is not used and therefore can be set to anything. Override the arguments with your Azure Credentials.

Parameter Position in Variable Name Description
--subscription-id Arg1 Subscription ID The Subscription ID of your Azure Subscription
--client-id Arg2 Client ID The Client ID of your Azure Subscription
--secret-key Arg3 Secret Key The Secret Key of your Azure Subscription
--tenant-id Arg4 Tenant ID The Tenant ID of your Azure Subscription

AZURE_RESOURCE_DETAILS

The Value is not used and therefore can be set to anything. Override the arguments with your Azure Resource Details.

Parameter Position in Variable Name Description
--resource-group Arg1 Resource Group Name of the Azure resource group of your resource
--resource-name Arg2 Resource Name Name of the Azure resource to be monitored

AZURE_SQL_DATABASE_DETAILS

The Value is not used and therefore can be set to anything. Override the arguments with your SQL Database Details.

Parameter Position in Variable Name Description
--sql-db-name Arg1 SQL Database Name The name of your Azure SQL Database

For more information, refer to Opsview Knowledge Center - Adding Variables to Hosts.

For mode-specific help, run the plugin with the -h -m flags. This will list the required and optional Variable Arguments for that mode. The appropriate mode for each Service Check is listed here:

Service Check Name Mode
Azure - SQL - Hyperscale - Allocated Storage SQL.Hyper.Allocated.Storage
Azure - SQL - Hyperscale - Connections SQL.Hyper.Connections
Azure - SQL - Hyperscale - CPU Usage SQL.Hyper.CPU.Percent
Azure - SQL - Hyperscale - CPU Used SQL.Hyper.CPU.Used
Azure - SQL - Hyperscale - Data IO Percent SQL.Hyper.Data.IO.Percent
Azure - SQL - Hyperscale - Deadlocks SQL.Hyper.Deadlocks
Azure - SQL - Hyperscale - Log IO Percent SQL.Hyper.Log.IO.Percent
Azure - SQL - Hyperscale - Process CPU Usage SQL.Hyper.Process.CPU.Usage
Azure - SQL - Hyperscale - Process Memory Usage SQL.Hyper.Process.Memory.Usage
Azure - SQL - Hyperscale - Sessions Percent SQL.Hyper.Sessions.Percent
Azure - SQL - Hyperscale - Tempdb Percent SQL.Hyper.Tempdb.Percent
Azure - SQL - Hyperscale - Tempdb Used SQL.Hyper.Tempdb.Used
Azure - SQL - Hyperscale - Workers Percent SQL.Hyper.Workers.Percent
Azure - SQL - Hyperscale - XTP Storage Percent SQL.Hyper.XTP.Storage.Percent

Step 3: Apply changes and the system will now be monitored

Azure SQL Hyperscale Output