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
In Azure Database for MySQL - Flexible Server, the error log is available to users to configure and access. Error logs in MySQL gather diagnostic messages during server startup and shutdown, and while the server is running, information that can help proactive troubleshooting. For more information about the MySQL error log, see the [Error log](https://dev.mysql.com/doc/refman/8.0/en/error-log.html) section in the MySQL documentation.
17
17
Under Preview phase, error logs are available under Server logs only, error logs **can't be emitted** to [Azure Diagnostic logs](./../../azure-monitor/essentials/platform-logs-overview.md).
18
18
19
19
>[!Note]
20
-
>The Error Log feature is accessible for new servers created after *1st December 2023*. For existing servers, this feature will become available following their scheduled maintenance in January 2024. To enable the Error Log feature on existing servers, before January 2024, kindly contact us via [support ticket](./../../azure-portal/supportability/how-to-manage-azure-support-request.md).
20
+
>The Error Log feature is accessible for new servers created after *November 14, 2023, 00:00 UTC*. For existing servers, this feature will become available following their scheduled maintenance in January 2024. [Learn more about scheduled maintainence](./concepts-maintenance.md) on your server. To enable the Error Log feature on existing servers, before the scheduled maintainence, kindly contact us via [support ticket](./../../azure-portal/supportability/how-to-manage-azure-support-request.md).
21
21
22
22
In Azure Database for MySQL - Flexible Server, enabling the error log under [Server logs](./concepts-monitoring.md#server-logs) in the Azure portal records details in multiple files named using the syntax *mysql-error-servername-timestamp.log*. In the file name, the timestamp (in GMT/UTC) associated with when the file was generated is appended, identifying the specific time that that log entries were recorded. For more information, see [Server logs retention.](./concepts-monitoring.md#server-logs)
23
23
24
-
## Enabling Error logs (Preview)
24
+
## Enabling error logs (Preview)
25
25
26
-
Users can access and configure the error logs in Azure Database for MySQL – Flexible Server via the Server logs feature, which can be enabled using the [Azure portal](./how-to-server-logs-portal#enable-server-logs) or [Azure CLI](./how-to-server-logs-cli.md).
26
+
Users can access and configure the error logs in Azure Database for MySQL – Flexible Server via the Server logs feature, which can be enabled using the [Azure portal](./how-to-server-logs-portal#enable-server-logs) or [Azure CLI](./how-to-server-logs-cli.md).
27
27
After the feature is enabled, your MySQL flexible server starts capturing events and writes them to a series of files saved as activity occurs.
28
28
29
29
To enable Error logs, perform the following steps.
30
30
1. In the Azure portal, navigate to your flexible server, and then, under Monitoring, select Server logs.
31
31
2. Under Server logs, select the Enable check box, which enables the server logs features
32
32
3. Under Select logs to enable, select the Error logs check box.
@@ -40,15 +40,15 @@ You can also enable Error logs on your Azure Database for MySQL flexible server
40
40
41
41
Ensure that the [Server logs feature](./how-to-server-logs-portal.md#enable-server-logs) is activated by selecting the *Enable* checkbox in the Server logs pane. Alternatively, set the server parameter "log_output" to FILE to enable server logs. Failure to perform either of these actions result in FILE logging not being enabled for your Azure Database for MySQL flexible server.
42
42
43
-
## Accessing Error logs
43
+
## Accessing error logs
44
44
You can download the error logs for further analysis of your Azure Database for MySQL flexible server. To download the logs, in the Azure portal, navigate to the Server logs section, and then select the Error logs tab, as shown.
45
45
- Under **Name**, select the log file you want to download, and then, under **Action**, select **Download**.
@@ -65,7 +65,7 @@ az mysql flexible-server server-logs download --resource-group <myresourcegroup>
65
65
For more information, see [how to download the server logs files](./how-to-server-logs-portal.md#download-server-logs) via the Azure portal or via the [Azure CLI](./how-to-server-logs-cli.md#downloading-server-logs-using-azure-cli).
66
66
67
67
68
-
### Error logs under Server logs retention
68
+
### Error logs under server logs retention
69
69
When logging is enabled for an Azure Database for MySQL - Flexible Server, logs are available up to seven days from their creation. If the total size of the available logs exceeds 7 GB, then the oldest files are deleted until space is available. The 7-GB storage limit for server logs is available free of cost and can't be extended. Logs are rotated every 24 hours or 500 MB, whichever comes first.
70
70
Importantly, you can download the logs before rotation, ensuring they have access to valuable server logs at any point within the retention period.
71
71
For more detailed information on log rotation schedules and storage limits for various log types, refer to the [documentation on Server log retention](./concepts-monitoring.md#server-logs).
Copy file name to clipboardExpand all lines: articles/mysql/flexible-server/concepts-monitoring.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.date: 9/21/2020
15
15
16
16
Azure Database for MySQL - Flexible Server provides monitoring of servers through Azure Monitor. Monitoring data about your servers helps you troubleshoot and optimize for your workload.
17
17
18
-
In this article, you'll learn about the various metrics available and Server logs for your flexible server that give insight into the behavior of your server.
18
+
In this article, you learn about the various metrics available and Server logs for your flexible server that give insight into the behavior of your server.
19
19
20
20
> [!NOTE]
21
21
> This article contains references to the term *slave*, a term that Microsoft no longer uses. When the term is removed from the software, we'll remove it from this article.
@@ -42,7 +42,7 @@ These metrics are available for Azure Database for MySQL:
42
42
|Active Connections|active_connection|Count|The number of active connections to the server. Active connections are the total number of [threads connected](https://dev.mysql.com/doc/refman/8.0/en/server-status-variables.html#statvar_Threads_connected) to your server, which also includes threads from [azure_superuser](../single-server/how-to-create-users.md).|
43
43
|Storage IO percent|io_consumption_percent|Percent|The percentage of IO in use over selected period. IO percent is for both read and write IOPS.|
44
44
|Storage IO Count|storage_io_count|Count|The total count of I/O operations (both read and write) utilized by server per minute.|
45
-
|Host Memory Percent|memory_percent|Percent|The total percentage of memory in use on the server, including memory utilization from both database workload and other Azure MySQL processes. This metric provides evaluation of the server's memory utilization, excluding re-usable memory like buffer and cache.|
45
+
|Host Memory Percent|memory_percent|Percent|The total percentage of memory in use on the server, including memory utilization from both database workload and other Azure MySQL processes. This metric provides evaluation of the server's memory utilization, excluding reusable memory like buffer and cache.|
46
46
|Available Memory Bytes|available_memory_bytes|Bytes|This metric represents the amount of memory that is currently available for use on the server.|
47
47
|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.|
48
48
|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).|
@@ -107,7 +107,7 @@ These metrics are available for Azure Database for MySQL:
107
107
|Metric display name|Metric|Unit|Description|
108
108
|---|---|---|---|
109
109
|InnoDB Row Lock Time|innodb_row_lock_time|Milliseconds|InnoDB row lock time measures the duration of time in milliseconds for InnoDB row-level locks.|
110
-
|InnoDB Row Lock Waitss|innodb_row_lock_waits|Count|InnoDB row lock waits count the number of times a query had to wait for an InnoDB row-level lock.|
110
+
|InnoDB Row Lock Waits|innodb_row_lock_waits|Count|InnoDB row lock waits count the number of times a query had to wait for an InnoDB row-level lock.|
111
111
|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.|
112
112
|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.|
113
113
|Innodb_buffer_pool_pages_free|Innodb_buffer_pool_pages_free|Count|The total count of free pages in InnoDB buffer pool.|
@@ -121,14 +121,14 @@ These metrics are available for Azure Database for MySQL:
121
121
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.
122
122
The server logs feature is disabled by default. For information about how to enable server logs, see [How to enable and download server logs for Azure Database for MySQL - Flexible Server.](./how-to-server-logs-portal.md)
123
123
124
-
Server logs supports[slow query logs](./concepts-slow-query-logs.md) and [error logs](./concepts-error-logs.md) for enabling and downloading.
124
+
Server logs support[slow query logs](./concepts-slow-query-logs.md) and [error logs](./concepts-error-logs.md) for enabling and downloading.
125
125
To perform a historical analysis of your data, in the Azure portal, on the Diagnostics settings pane for your server, add a diagnostic setting to send the logs to Log Analytics workspace, Azure Storage, or event hubs. For more information, see [Set up diagnostics](./tutorial-query-performance-insights.md#set-up-diagnostics).
126
126
127
127
**Server logs retention**
128
128
129
129
When logging is enabled for an Azure Database for MySQL - Flexible Server, all the logs, *including error logs and slow query logs* are available up to seven days from their creation. If the total size of all the available logs exceeds 7 GB, then the oldest files are deleted until space is available.
130
130
The 7-GB storage limit for server logs is available free of cost and can't be extended.
131
-
Logs are rotated every 24 hours or 500MB, whichever comes first.
131
+
Logs are rotated every 24 hours or 500 MB, whichever comes first.
Copy file name to clipboardExpand all lines: articles/mysql/flexible-server/overview.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,7 +80,7 @@ You have two networking options to connect to your Azure Database for MySQL - Fl
80
80
81
81
-**Private access (VNet Integration)** – You can deploy your flexible server into your [Azure Virtual Network](../../virtual-network/virtual-networks-overview.md). Azure virtual networks provide private and secure network communication. Resources in a virtual network can communicate through private IP addresses.
82
82
83
-
Choose the VNet Integration option if you want the following capabilities:
83
+
Choose the virtual network Integration option if you want the following capabilities:
84
84
85
85
- Connect from Azure resources in the same virtual network to your flexible server using private IP addresses
86
86
- Use VPN or ExpressRoute to connect from non-Azure resources to your flexible server
@@ -106,11 +106,11 @@ The read replica feature allows you to replicate data from an Azure Database for
106
106
107
107
For more information, see [Read Replica concepts](concepts-read-replicas.md).
108
108
109
-
## Setup Hybrid or Multi-Cloud Data synchronization with Data-in replication
109
+
## Setup Hybrid or multicloud Data synchronization with Data-in replication
110
110
111
111
Data-in replication allows you to synchronize data from an external MySQL server into the Azure Database for MySQL Flexible Server. The external server can be on-premises, in virtual machines, Azure Database for MySQL Single Server, or a database service hosted by other cloud providers. Data-in replication is based on the binary log (binlog) file position-based. The main scenarios to consider about using Data-in replication are:
112
112
* Hybrid Data Synchronization
113
-
*Multi-Cloud Synchronization
113
+
*Multicloud Synchronization
114
114
*[Minimal downtime migration to Flexible Server](../../mysql/howto-migrate-single-flexible-minimum-downtime.md)
115
115
116
116
For more information, see [Data-in replication concepts](concepts-data-in-replication.md).
0 commit comments