Preconfigured dashboards and alerts for Azure metrics

Cloud Provider Observability provides the following preconfigured dashboards and alerts for you to install in your Grafana Cloud instance. These dashboards are embedded in and accessible in the Azure observability section of Cloud Provider Observability in Grafana Cloud.

Preconfigured dashboards

Preconfigured dashboards are available for the following Azure resources. Click the links to view details on the default metrics pulled from Azure Monitor metrics.

Azure Application Gateway metrics: Microsoft.Network/applicationgateways
Azure Blob Storage metrics: Microsoft.Storage/storageAccounts/blobServices
Azure SQL Database - Elastic Pools metrics: Microsoft.Sql/servers/elasticpools
Azure Event Hub metrics: Microsoft.EventHub/Namespaces
Azure Front Door metrics: Microsoft.Cdn/profiles
Azure Load Balancing metrics: Microsoft.Network/loadBalancers
Azure PostgreSQL Flexible Servers metrics: Microsoft.DBforPostgreSQL/flexibleServers
Azure Queue Storage metrics: Microsoft.Storage/storageAccounts/queueServices
Azure Service Bus metrics: Microsoft.ServiceBus/Namepaces
Azure SQL Database metrics: Microsoft.Sql/servers/databases
Azure Virtual Machines metrics: Microsoft.Compute/virtualMachines
Azure Virtual Network metrics: Microsoft.Network/virtualNetworks

Go to an Azure dashboard

To see any metrics dashboard, configure Azure metrics.
In the main menu, click Azure to open the Services tab.
List of available services on Services tab
Locate the specific service in the list, and click the name of the service in the Service column of the table.

Filter dashboards

You can use the filters on any dashboard to refine your data. Filters are appropriate for each dashboard, and may include:

Data source
Job
Resource group
Subscription name
Resource name
Bucket name
Instance
Namespace

Additionally, use the time range selector to change time period of your data.

View predictions

For the preconfigured dashboards that include drilldown information for specific instances, Cloud Provider Observability includes machine learning predictions. Predictions can help you ensure resources are available during spikes in usage, as well as help you decrease the amount of unused resources due to over provisioning. To use prediction tools, first enable LLM features for your Grafana instance.

You can view the prediction model for various metrics by clicking the Predict button in the top right corner of the panel.

Screenshot of a panel with the Predict button and time range filter highlighted

Use the time range filter to adjust the time range to show more advanced predictions. The time range you select must be at least two hours to use the prediction tool.

For more information on the terminology included and how machine learning works in the prediction graph, refer to the Query Metrics page in the AI and machine learning documentation.

Preconfigured alerts

When you configure Azure metrics, the following prebuilt alerts are available. Alerts are organized by alert severity level.

Critical

AzureDatabaseHighDtuConsumption: Fires if your resource’s database his high database transaction unit consumption. You need to check active queries and optimize indexes or consider scaling up database transaction units to handle load in the specified resource’s database.
AzureDatabaseHighStorageUsage: Fires if your resource’s database has high database storage usage. You need to archive or delete old data, or scale up storage capacity in the specified resource’s database.
AzureDatabaseHighWorkerUsage: Fires if your resource’s database has high database worker usage. You need to look for long execution queries, review the number of concurrent queries and requests being sent to the database or check if there are any blocking sessions or deadlocks into the specified resource’s database.
AzureDatabaseLowTempdbLogSpace: Fires if your resource’s database has low tempdb log space. You need to look for active sessions that might be using tempdb intensively, identify stored procedures or queries that create temporary tables or objects, and also look for long-running or memory-intensive queries that rely heavily on tempdb into the specified resource’s database.
AzureVMHighCpuUtilization: Fires if your virtual machine’s CPU utilization is too high, indicating the specified virtual machine is under heavy load and may become unresponsive.
AzureVMUnavailable: Fires if your virtual machine is unavailable, indicating the specified virtual machine is not functioning or crashed, which may require immediate action.
AzureVNetPeeringConnectionFailures: Fires if you have Azure VirtualNetwork(VNet) peering connection issues, meaning the success rate of the specified Virtual Network peering connections has fallen below the defined threshold, indicating possible connectivity failures. You need to investigate potential misconfigurations, network latency, or service disruptions affecting peering communication.
AzureVNetSubnetIPExhaustion: Fires if your Azure Virtual Network(VNet) has subnet IP exhaustion. IP addresses for the specified subnet on the specified Virtual network have dropped below the critical threshold. This issue may cause connectivity issues for new resources requiring IP allocations. You need to resize the subnet or optimize IP usage.

Warning

AzureDatabaseHighSystemFailedConnections: Fires if your resource’s database has a high number of database system failed connections. You need to check network problems, firewall restrictions or high resource consumption affecting application access to the specified resource’s database.
AzureDatabaseHighUserCpuUsage: Fires if your resource’s database has high database user CPU usage. You need to identify high CPU queries on the specified resource’s database and optimize them.
AzureDatabaseHighUserFailedConnections: Fires if your resource’s database has a high number of database user failed connections. You need to check for authentication problems, network configuration errors, firewall issues, or resource constraints, affecting database accessibility for users on the specified resource’s database.

Info

AzureDatabaseHighDataIoUsage: Fires if your database has high data IO usage. You need to review queries with high read or write activity, check if there are missing indexes or inefficient indexes that result in full table scans and assess the volume of transactions into the specified resource’s database.
AzureDatabaseHighDeadlockCount: Fires if your database has high Deadlock count. You need to check the specified resource’s database logs for deadlock details and optimize affected queries.