You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/mysql/flexible-server/concepts-monitoring.md
+35Lines changed: 35 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,8 +48,43 @@ These metrics are available for Azure Database for MySQL:
48
48
|Total connections|total_connections|Count|The number of client connections to your Azure Database for MySQL Flexible server. Total Connections is sum of connections by clients using TCP/IP protocol over a selected period.|
49
49
|Aborted Connections|aborted_connections|Count|Total number of failed attempts to connect to your MySQL server, for example, failed connection due to bad credentials. For more information on aborted connections, you can refer to this [documentation](https://dev.mysql.com/doc/refman/5.7/en/communication-errors.html).|
50
50
|Queries|queries|Count|Total number of queries executed per minute on your server. Total count of queries per minute on your server from your database workload and Azure MySQL processes.|
51
+
|Slow_queries|slow_queries|Count|The total count of slow queries on your server in the selected time range.|
51
52
52
53
54
+
## Enhanced metrics
55
+
56
+
57
+
### DML statistics
58
+
59
+
|Metric display name|Metric|Unit|Description|
60
+
|---|---|---|---|
61
+
|Com_select|Com_select|Count|The total count of select statements that have been executed on your server in the selected time range.|
62
+
|Com_update|Com_update|Count|The total count of update statements that have been executed on your server in the selected time range.|
63
+
|Com_insert|Com_insert|Count|The total count of insert statements that have been executed on your server in the selected time range.|
64
+
|Com_delete|Com_delete|Count|The total count of delete statements that have been executed on your server in the selected time range.|
65
+
66
+
67
+
### DDL statistics
68
+
69
+
|Metric display name|Metric|Unit|Description|
70
+
|---|---|---|---|
71
+
|Com_create_db|Com_create_db|Count|The total count of create database statements that have been executed on your server in the selected time range.|
72
+
|Com_drop_db|Com_drop_db|Count|The total count of drop database statements that have been executed on your server in the selected time range.|
73
+
|Com_create_table|Com_create_table|Count|The total count of create table statements that have been executed on your server in the selected time range.|
74
+
|Com_drop_table|Com_drop_table|Count|The total count of drop table statements that have been executed on your server in the selected time range.|
75
+
|Com_Alter|Com_Alter|Count|The total count of alter table statements that have been executed on your server in the selected time range.|
76
+
77
+
78
+
### Innodb metrics
79
+
80
+
|Metric display name|Metric|Unit|Description|
81
+
|---|---|---|---|
82
+
|Innodb_buffer_pool_reads|Innodb_buffer_pool_reads|Count|The total count of logical reads that InnoDB engine couldn't satisfy from the Innodb buffer pool, and had to be fetched from the disk.|
83
+
|Innodb_buffer_pool_read_requests|Innodb_buffer_pool_read_requests|Count|The total count of logical read requests to read from the Innodb Buffer pool.|
84
+
|Innodb_buffer_pool_pages_free|Innodb_buffer_pool_pages_free|Count|The total count of free pages in InnoDB buffer pool.|
85
+
|Innodb_buffer_pool_pages_data|Innodb_buffer_pool_pages_data|Count|The total count of pages in the InnoDB buffer pool containing data. The number includes both dirty and clean pages.|
86
+
|Innodb_buffer_pool_pages_dirty|Innodb_buffer_pool_pages_dirty|Count|The total count of pages in the InnoDB buffer pool containing dirty pages.|
87
+
53
88
## Server logs
54
89
55
90
In Azure Database for MySQL Server – Flexible Server, users can configure and download server logs to assist with troubleshooting efforts. With this feature enabled, a flexible server starts capturing events of the selected log type and writes them to a file. You can then use the Azure portal and Azure CLI to download the files to work with them.
Copy file name to clipboardExpand all lines: articles/mysql/flexible-server/whats-new.md
+15-2Lines changed: 15 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,20 @@ This article summarizes new releases and features in Azure Database for MySQL -
30
30
31
31
-**Autoscale IOPS in Azure Database for MySQL - Flexible Server**
32
32
33
-
You can now scale IOPS on demand without having to pre-provision a certain amount of IOPS. With this feature, you can now enjoy worry free IO management in Azure Database for MySQL - Flexible Server because the server scales IOPs up or down automatically depending on workload needs. With this feature you pay only for the IO you use and no longer need to provision and pay for resources they aren’t fully using, saving both time and money. In addition, mission-critical Tier-1 applications can achieve consistent performance by making additional IO available to the workload at any time. Auto scale IO eliminates the administration required to provide the best performance at the least cost for Azure Database for MySQL customers. [Learn more](./concepts-service-tiers-storage.md)
33
+
You can now scale IOPS on demand without having to pre-provision a certain amount of IOPS. With this feature, you can now enjoy worry free IO management in Azure Database for MySQL - Flexible Server because the server scales IOPs up or down automatically depending on workload needs. With this feature you, pay only for the IO you use and no longer need to provision and pay for resources they aren’t fully using, saving both time and money. In addition, mission-critical Tier-1 applications can achieve consistent performance by making additional IO available to the workload at any time. Auto scale IO eliminates the administration required to provide the best performance at the least cost for Azure Database for MySQL customers. [Learn more](./concepts-service-tiers-storage.md)
34
+
35
+
-**Perform Major version upgrade with minimal efforts for Azure Database for MySQL - Flexible Server (Preview)**
36
+
37
+
The major version upgrade feature allows you to perform in-place upgrades of existing instances of Azure Database for MySQL - Flexible Server from MySQL 5.7 to MySQL 8.0 with the click of a button, without any data movement or the need to make any application connection string changes. Take advantage of this functionality to efficiently perform major version upgrades on your instances of Azure Database for MySQL - Flexible Server and leverage the latest that MySQL 8.0 has to offer. Learn [more](./how-to-upgrade.md).
38
+
39
+
-**MySQL extension for Azure Data Studio (Preview)**
40
+
41
+
When you’re working with multiple databases across data platforms and cloud deployment models, being able to perform the most common tasks on all your databases using a single tool enhances your productivity several fold. With the MySQL extension for Azure Data Studio, you can now connect to and modify MySQL databases along with your other databases, taking advantage of the modern editor experience and capabilities in Azure Data Studio, such as IntelliSense, code snippets, source control integration, native Jupyter Notebooks, an integrated terminal, and more. Use this new tooling with any MySQL server hosted on-premises, on virtual machines, on managed MySQL in other clouds, and on Azure Database for MySQL – Flexible Server. Learn [more](/sql/azure-data-studio/quickstart-mysql).
42
+
43
+
-**Known issues**
44
+
45
+
- Change of compute size is not currently permitted after the Major version upgrade of your Azure Database for MySQL - Flexible Server. It is recommended to change the compute size of your Azure Database for MySQL - Flexible Server before the major version upgrade from version 5.7 to version 8.0.
46
+
34
47
35
48
## September 2022
36
49
@@ -410,7 +423,7 @@ This release of Azure Database for MySQL - Flexible Server includes the followin
410
423
411
424
-**Support for Availability zone placement during server creation released**
412
425
413
-
Customers can now specify their preferred Availability zone at the time of server creation. This functionality allows customers to collocate their applications hosted on Azure VM, virtual machine scale set, or AKS and database in the same Availability zones to minimize database latency and improve performance. [Learn more](quickstart-create-server-portal.md#create-an-azure-database-for-mysql-flexible-server).
426
+
Customers can now specify their preferred Availability zone at the time of server creation. This functionality allows customers to collocate their applications hosted on Azure VM, Virtual Machine Scale Set, or AKS and database in the same Availability zones to minimize database latency and improve performance. [Learn more](quickstart-create-server-portal.md#create-an-azure-database-for-mysql-flexible-server).
414
427
415
428
-**Performance fixes for issues when running flexible server in virtual network with private access**
0 commit comments