<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Microsoft Azure SQL Database Sensor

Permissions for the Azure custom role

This sensor requires an Azure custom role with specific permissions. Create an Azure custom role and add permissions for the following actions:

• "Microsoft.Sql/servers/*/read",
• "Microsoft.Insights/Metrics/providers/Metrics/Read",
• "Microsoft.Insights/Metrics/Microsoft.Insights/Read",
• "Microsoft.Insights/Metrics/Read",
• "Microsoft.Insights/Metricnamespaces/Read",
• "Microsoft.Insights/MetricDefinitions/providers/Microsoft.Insights/Read",
• "Microsoft.Insights/Components/providers/Microsoft.Insights/MetricDefinitions/Read"

For more information, see the Knowledge Base: How do I obtain credentials and create custom roles for the Microsoft Azure sensors?

Sensor Name

Enter a name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets.

If the name contains angle brackets (<>), PRTG replaces them with braces ({}) for security reasons. For more information, see the Knowledge Base: What security features does PRTG include?

Parent Tags

The tags that the sensor inherits from its parent device, parent group, and parent probe.

This setting is for your information only. You cannot change it.

Tags

Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited.

It is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).

For performance reasons, it can take some minutes until you can filter for new tags that you added.

The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:

• microsoftazure
• microsoftazuresqldatabase
• azure

Priority

Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority () to the highest priority ().

Azure SQL Database Name

The name of the Azure SQL Database that this sensor monitors.

If you change the database name in your Microsoft Azure subscription, you must add the sensor anew.

Azure SQL Database ID

The ID of the Azure SQL Database that this sensor monitors.

Azure SQL Server Name

The name of the Azure SQL server that hosts the Azure SQL Database.

Resource Type

The resource type of the Azure SQL Database that this sensor monitors. This can be a single database or an elastic pool in a virtual core (vCore) based purchasing model or a DTU-based purchasing model.

If you change the resource type in your Microsoft Azure subscription, you must add the sensor anew.

Region

The Azure region of the Azure SQL Database that this sensor monitors.

Purchasing Model

The purchasing model of the Azure SQL Database. This can be vCore based or DTU based.

Elastic Pool

The name of the elastic pool if the resource type of the Azure SQL Database is an elastic pool. If the resource type is not an elastic pool, the field shows n/a.

Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor.

You can set a different primary channel later by clicking below a channel gauge on the sensor's Overview tab.

Graph Type

Define how different channels are shown for this sensor:

• Show channels independently (default): Show a graph for each channel.
• Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
  You cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).

Stack Unit

This setting is only visible if you select Stack channels on top of each other above.

Select a unit from the list. All channels with this unit are stacked on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so.

Result Handling

Define what PRTG does with the sensor result:

• Discard result (default): Do not store the sensor result.

• Store result: Store the last sensor result in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file name is Result of Sensor [ID].log. This setting is for debugging purposes. PRTG overwrites this file with each scanning interval.

This option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance.

In a cluster, PRTG stores the result in the PRTG data directory of the master node.

Connections Failed

The number of failed connections

CPU Used %

The CPU usage (%)

This channel is the primary channel by default.

Data I/O %

The data I/O operations (%)

Data Space Used

The data space usage

Data Space Used %

The data space usage (%)

Deadlocks

The number of deadlocks

Downtime

In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status

DTU %

The DTUs (%)

DTU Limit

The DTU limit

DTU Used

The used DTU

eDTU Limit

The eDTU limit

eDTU Used

The used eDTU

Log I/O

The log I/O operations

Sessions %

The sessions (%)