Monitoring Azure MySQL Database
Instana offers comprehensive monitoring of your Azure MySQL Database, providing end-to-end visibility into your environment. After you install the Instana host agent, the Azure MySQL Database sensor is automatically deployed and installed. You can view infrastructure metrics that are related to Azure MySQL Database in the Instana UI.
For more information about the other supported Azure services, see the Azure documentation.
Supported information
Supported client-side tracing
For this technology, Instana supports client-side tracing for the following languages and runtimes:
Configuring the Azure MySQL Database sensor
To monitor your Azure MySQL Database, you need to first enable the Azure sensor in the agent configuration.yaml file as follows. For more information, see Installation.
com.instana.plugin.azure:
enabled: true
subscription: "[Your-Subscription-Id]"
tenant: "[Your-Tenant-Id]"
principals:
- id: "[Your-Service-Principal-Account-Id]"
secret: "[Your-Service-Principal-Secret]"
To configure the Azure MySQL Database sensor through the agent configuration file <agentinstall_dir>/etc/instana/configuration.yaml, use the following configuration:
com.instana.plugin.azure.mysql:
# Valid values: true, false
enabled: false # enabled (true) by default
# Comma separated list of tags in key:value format
include_tags:
# Comma separated list of tags in key:value format
exclude_tags:
# Comma separated list of resource groups
include_resource_groups:
# Comma separated list of resource groups
exclude_resource_groups:
You can disable the Azure MySQL Database sensor and filter it by tags and resource groups.
Disabling the sensor
To disable monitoring of the Azure MySQL Database services, use the following configuration:
com.instana.plugin.azure.mysql:
enabled: false
Filtering by defining tags and resource groups
You can define multiple tags and resource groups, which are separated by a comma. The tags must be defined as a key-value pair separated by a colon (:). To configure easily, define the tags and resource groups that you want to
include in discovery or exclude from discovery. If you define a tag or resource group in both lists (include and exclude), the exclude list has a higher priority. If you don't want to filter services, you must not define the configuration.
You don't need to define all values to enable filtering.
To include services by tags into discovery, use the following configuration:
com.instana.plugin.azure.mysql:
include_tags: # Comma separated list of tags in key:value format (e.g. env:prod,env:staging)
To exclude services by tags from discovery, use the following configuration:
com.instana.plugin.azure.mysql:
exclude_tags: # Comma separated list of tags in key:value format (e.g. env:dev,env:test)
To include services by resource groups into discovery, use the following configuration:
com.instana.plugin.azure.mysql:
include_resource_groups: # Comma separated list of resource groups (e.g. rg_prod,rg_staging)
To exclude services by resource groups from discovery, use the following configuration:
com.instana.plugin.azure.mysql:
exclude_resource_groups: # Comma separated list of resource groups (e.g. rg_dev,rg_test)
Discovery filtering can be configured on the global level for all Azure services. In defining filters for the Azure MySQL Database service, global filters are overridden. For more information about global Azure service discovery filtering, see Azure Configuration.
Viewing metrics
To view the metrics, complete the following steps:
- In the sidebar of the Instana UI, select Infrastructure.
- Click a specific monitored host.
You can see a host dashboard with all the collected metrics and monitored processes.
Metrics are pulled every minute, which is the resolution Azure provides for monitoring of these services.
Configuration data
| Database Details | Description |
|---|---|
| Name | Database name |
| Domain Name | Fully qualified domain name of the database |
| Resource Group | Resource group of the database |
| Location | Database location |
| Subscription Id | Subscription ID of the database |
| Type | Type of the resource |
| State | State of the database |
| Version | Version of the database |
| Max Connections | Maximum permitted number of simultaneous client connections that are configured |
Performance metrics
| Metric | Unit | Aggregation | Description |
|---|---|---|---|
| Server Host | |||
| CPU Percent | Percent | Maximum | Total usage of the host CPU |
| Memory Percent | Percent | Maximum | Total percentage of memory that is in use on the server |
| Storage | |||
| Used | Bytes | Maximum | Amount of storage in use |
| Limit | Bytes | Maximum | Maximum storage for the server |
| Storage Percent | |||
| Used | Percent | Maximum | Percentage of storage used out of the maximum storage of the server |
| IO | Percent | Maximum | Percentage of input and output in use |
| Host Network | |||
| Out | Bytes | Total | Total sum of outgoing network traffic on the server |
| In | Bytes | Total | Total sum of incoming network traffic on the server |
| Connections | |||
| Active | Count | Maximum | Number of active connections to the server |
| Aborted | Count | Total | Total number of failed attempts to connect to the MySQL server |
| Total | Count | Total | The total number of client connections to your Azure Database for MySQL flexible server instance |
| Replication | |||
| Lag | Seconds | Maximum | Number of seconds by which the replica is behind in replaying the transactions that are received from the source server |
| Queries | |||
| Count | Count | Total | The total number of queries that are executed per minute on your server |
| SlowQueries | |||
| Count | Count | Total | The total number of slow queries that are executed per minute on your server |
| Create Statements | |||
| Create DB | Count | Total | The total number of create database statements that are executed on your server in the selected time range |
| Create Table | Count | Total | The total number of create table statements that are executed on your server in the selected time range |
| Drop Statements | |||
| Drop Table | Count | Total | The total number of drop table statements that are executed on your server in the selected time range |
| Drop Db | Count | Total | The total number of drop database statements that are executed on your server in the selected time range |
| Statements | |||
| Delete | Count | Total | The total number of delete statements that are executed on your server in the selected time range |
| Insert | Count | Total | The total number of insert statements that are executed on your server in the selected time range |
| Select | Count | Total | The total number of select statements that are executed on your server in the selected time range |
| Alter | Count | Total | The total number of alter table statements that are executed on your server in the selected time range |
| Update | Count | Total | The total number of update statements that are executed on your server in the selected time range |
Health signatures
Each sensor has a curated knowledgebase of health signatures that are evaluated continuously against the incoming metrics and are used to raise issues or incidents that depend on user impact.
Built-in events trigger issues or incidents based on failing health signatures on entities, and custom events trigger issues or incidents based on the thresholds of an individual metric of any specific entity.
For more information about built-in events for Azure MySQL Database Service sensor, see the Built-in events reference.