Azure Database for MySQL Flexible Servers monitoring

  • How-to guide
  • 3-min read
  • Published Aug 27, 2024

From 16 September 2024, Azure Database for MySQL Flexible Servers replaces Azure Database for MySQL Single Server.

The Azure Database for MySQL Flexible Servers overview page serves as a comprehensive overview of your MySQL servers and database instances. From here you can gain full visibility and check if your database is healthy, under-performing, or if there are any failed connections.

Prerequisites

  • Dynatrace version 1.298+
  • Environment ActiveGate version 1.195+

Enable monitoring

To learn how to enable service monitoring, see Enable service monitoring.

Optionally, for OneAgent integration, see how database activity is monitored.

View service metrics

You can view the service metrics in your Dynatrace environment either on the custom device overview page or on your Dashboards page.

View metrics on the custom device overview page

To access the custom device overview page

  1. Go to Technologies & Processes Classic.
  2. Filter by service name and select the relevant custom device group.
  3. Once you select the custom device group, you're on the custom device group overview page.
  4. The custom device group overview page lists all instances (custom devices) belonging to the group. Select an instance to view the custom device overview page.

View metrics on your dashboard

Once you add a service to monitoring, a preset dashboard for the respective service containing all recommended metrics is automatically created on your Dashboards page. You can look for specific dashboards by filtering by Preset and then by Name.

For existing monitored services, you might need to resave your credentials for the preset dashboard to appear on the Dashboards page. To resave your credentials, go to Settings > Cloud and virtualization > Azure, select the desired Azure instance, then select Save.

You can't make changes on a preset dashboard directly, but you can clone and edit it. To clone a dashboard, open the browse menu () and select Clone.
To remove a dashboard from the dashboards list, you can hide it. To hide a dashboard, open the browse menu () and select Hide.

Hiding a dashboard doesn't affect other users.

Clone hide azure

Available metrics

NameDescriptionUnitRecommended
aborted_connectionsAborted connectionsCountApplicable
active_connectionsActive connectionsCountApplicable
active_transactionsActive transactionsCount
backup_storage_usedBackup storage usedByte
binlog_storage_usedBinlog storage usedByte
cpu_credits_consumedCPU credits consumedCount
cpu_credits_remainingCPU credits remainingCount
Com_alter_tableCom alter tableCount
Com_create_dbCom create DBCount
Com_create_tableCom create tableCount
Com_deleteCom deleteCount
Com_drop_dbCom drop DBCount
Com_drop_tableCom drop tableCount
Com_insertCom insertCount
Com_selectCom selectCount
Com_updateCom updateCount
data_storage_usedData storage usedByte
HA_IO_statusHa IO statusCount
HA_SQL_statusHa SQL statusCount
HA_replication_lagHa replication lagSecond
cpu_percentHost CPU percentPercentApplicable
network_bytes_ingressHost network inByteApplicable
network_bytes_egressHost network outByteApplicable
ibdata1_storage_usedIbdata1 storage usedByte
Innodb_buffer_pool_pages_dataInnodb buffer pool pages dataCount
Innodb_buffer_pool_pages_dirtyInnodb buffer pool pages dirtyCount
Innodb_buffer_pool_pages_flushedInnodb buffer pool pages flushedCount
Innodb_buffer_pool_pages_freeInnodb buffer pool pages freeCount
Innodb_buffer_pool_readsInnodb buffer pool readsCount
Innodb_data_writesInnodb data writesCount
Innodb_row_lock_timeInnodb row lock timeMilliSecond
Innodb_row_lock_waitsInnodb row lock waitsCount
memory_percentMemory percentPercentApplicable
trx_rseg_history_lenMysql history list lengthCount
lock_deadlocksMysql lock deadlocksCount
lock_timeoutsMysql lock timeoutsCount
UptimeMysql uptimeSecond
others_storage_usedOthers storage usedByte
QueriesQueriesCount
Replica_IO_RunningReplica IO statusCount
Replica_SQL_RunningReplica SQL statusCount
replication_lagReplication lag in secondsSecondApplicable
serverlog_storage_limitServerlog storage limitByte
serverlog_storage_percentServerlog storage percentPercentApplicable
serverlog_storage_usageServerlog storage usedByte
Slow_queriesSlow queriesCount
storage_io_countStorage IO countCount
io_consumption_percentStorage IO percentPercentApplicable
storage_limitStorage limitByte
storage_percentStorage percentPercent
storage_usedStorage usedByte
Threads_runningThreads runningCount
total_connectionsTotal connectionsCount
Related tags
Infrastructure Observability