Merge pull request #261342 from code-sidd/new_error_log

erro log and other changes

Author: v-dirichards

articles/mysql/TOC.yml

@@ -120,6 +120,8 @@
         href: flexible-server/concepts-monitoring.md
       - name: Slow query Logs
         href: flexible-server/concepts-slow-query-logs.md
+      - name: Error logs
+        href: flexible-server/concepts-error-logs.md        
       - name: Audit logs
         href: flexible-server/concepts-audit-logs.md
       - name: Workbooks

articles/mysql/flexible-server/concepts-error-logs.md

@@ -0,0 +1,85 @@
+---
+title: 'Error logs - Azure Database for MySQL - Flexible Server'
+description: This article describes the error logs feature for Azure Database for MySQL - Flexible Server.
+ms.service: mysql
+ms.subservice: flexible-server
+ms.topic: conceptual
+author: code-sidd
+ms.author: sisawant
+ms.date: 12/15/2023
+---
+
+# Error logs in Azure Database for MySQL - Flexible Server (Preview)
+
+[!INCLUDE[applies-to-mysql-flexible-server](../includes/applies-to-mysql-flexible-server.md)]
+
+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. 
+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).
+
+>[!Note]
+>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).
+
+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)
+
+## Enabling error logs (Preview)
+
+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.md#enable-server-logs) or [Azure CLI](./how-to-server-logs-cli.md). 
+After the feature is enabled, your MySQL flexible server starts capturing events and writes them to a series of files saved as activity occurs.
+
+To enable Error logs, perform the following steps.
+1.	In the Azure portal, navigate to your flexible server, and then, under Monitoring, select Server logs.
+2.	Under Server logs, select the Enable check box, which enables the server logs features
+3.	Under Select logs to enable, select the Error logs check box.
+
+    :::image type="content" source="./media/concepts-error-logs/1-concepts-error-logs.png" alt-text="Screenshot of portal view showing Error Logs - Enable.":::
+
+4.	Select Save to proceed with deployment.
+
+
+You can also enable Error logs on your Azure Database for MySQL flexible server by [enabling the server parameter](./how-to-configure-server-parameters-portal.md) named *“error_server_log_file”*  via the Server parameters pane or via the [Azure CLI](./how-to-configure-server-parameters-cli.md). 
+
+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.
+
+## Accessing error logs 
+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.
+ - Under **Name**, select the log file you want to download, and then, under **Action**, select **Download**. 
+ 
+    :::image type="content" source="./media/concepts-error-logs/2-concepts-error-logs.png" alt-text="Screenshot of portal view showing Error Logs - Download.":::
+
+ - To download *multiple log files* at one time, under **Name**, select the files you want to download, select **Download**.
+ 
+    :::image type="content" source="./media/concepts-error-logs/3-concepts-error-logs.png" alt-text="Screenshot of portal view showing Error Logs - Multiple Downloads.":::
+    
+
+### Access error logs using Azure CLI
+You can list the server logs from your flexible server by using the following command.
+```azurecli
+az mysql flexible-server server-logs list --resource-group <myresourcegroup>  --server-name <server_name> --out table 
+```
+
+To download the mentioned server logs to your current directory, use the following command:
+```azurecli
+az mysql flexible-server server-logs download --resource-group <myresourcegroup> --server-name <server_name>  --name <mysql-error-<server_name>-<timestamp>.log>
+```
+
+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).
+
+
+### Error logs under server logs retention
+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. 
+Importantly, you can download the logs before rotation, ensuring they have access to valuable server logs at any point within the retention period.
+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).
+
+
+## Frequently asked questions
+
+*Question*: My error logs contain the note as shown, what does this mean?
+
+`[Note] [Server] Access denied for user ''@'xx.xx.xx.X' (using password: NO).`
+
+*Answer*: This note indicates that an attempt to connect to your MySQL server was unsuccessful due to incorrect or missing authentication details. Specifically, the username provided is empty(''@'xx.xx.xx.X') and no password was entered (using password: NO). This note could indicate an unauthorized attempt to access your database.
+If your server is publicly accessible, it remains exposed to the internet and can be a target for unauthorized access attempts. To enhance the security of your Azure Database for MySQL flexible server, [disable public access](./concepts-networking-private-link.md#deny-public-access) or [limit access using firewall rules.](./concepts-networking-public.md#firewall-rules).
+
+## Next steps
+- How to enable server logs feature via Azure portal. [Learn more](./how-to-server-logs-portal.md)
+- How to enable server logs feature via Azure CLI. [Learn more](./how-to-server-logs-cli.md)

articles/mysql/flexible-server/concepts-monitoring.md

@@ -15,7 +15,7 @@ ms.date: 9/21/2020
 
 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.
 
-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.
+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.
 
 > [!NOTE]
 > 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:
 |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).|
 |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.|
 |Storage IO Count|storage_io_count|Count|The total count of I/O operations (both read and write) utilized by server per minute.|
-|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.|
+|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.|
 |Available Memory Bytes|available_memory_bytes|Bytes|This metric represents the amount of memory that is currently available for use on the server.|
 |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.|
 |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:
 |Metric display name|Metric|Unit|Description|
 |---|---|---|---|
 |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.|
-|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.|
+|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.|
 |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.|
 |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.|
 |Innodb_buffer_pool_pages_free|Innodb_buffer_pool_pages_free|Count|The total count of free pages in InnoDB buffer pool.|
@@ -119,16 +119,16 @@ These metrics are available for Azure Database for MySQL:
 ## Server logs
 
 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.
-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)
+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)
 
+Server logs support [slow query logs](./concepts-slow-query-logs.md) and [error logs](./concepts-error-logs.md) for enabling and downloading.
 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).
 
 **Server logs retention**
 
-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.
+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.
 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 7 GB, whichever comes first.
+Logs are rotated every 24 hours or 500 MB, whichever comes first.
 
 
 ## Next steps

articles/mysql/flexible-server/media/concepts-error-logs/1-concepts-error-logs.png

@@ -80,7 +80,7 @@ You have two networking options to connect to your Azure Database for MySQL - Fl
 
 - **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.
 
-  Choose the VNet Integration option if you want the following capabilities:
+  Choose the virtual network Integration option if you want the following capabilities:
 
   - Connect from Azure resources in the same virtual network to your flexible server using private IP addresses
   - 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
 
 For more information, see [Read Replica concepts](concepts-read-replicas.md).
 
-## Setup Hybrid or Multi-Cloud Data synchronization with Data-in replication
+## Setup Hybrid or multicloud Data synchronization with Data-in replication
 
 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:
 * Hybrid Data Synchronization
-* Multi-Cloud Synchronization
+* Multicloud Synchronization
 * [Minimal downtime migration to Flexible Server](../../mysql/howto-migrate-single-flexible-minimum-downtime.md)
 
 For more information, see [Data-in replication concepts](concepts-data-in-replication.md).
@@ -185,6 +185,7 @@ One advantage of running your workload in Azure is its global reach. The flexibl
 | France Central | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
 | France South | :heavy_check_mark: | :heavy_check_mark: | :x: | :heavy_check_mark: |
 | Germany West Central | :heavy_check_mark: | :heavy_check_mark: | :x: | :heavy_check_mark: |
+| Israel Central | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :x: |
 | Japan East | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
 | Japan West | :heavy_check_mark: | :heavy_check_mark: | :x: | :heavy_check_mark: |
 | Korea Central | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
@@ -194,7 +195,7 @@ One advantage of running your workload in Azure is its global reach. The flexibl
 | Norway East | :heavy_check_mark: | :heavy_check_mark: | :x: | :x: |
 | Norway West | :heavy_check_mark: | :heavy_check_mark: | :x: | :x: |
 | Qatar Central | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :x: |
-| South Africa North | :heavy_check_mark: | :heavy_check_mark: | :x: | :x: |
+| South Africa North | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :x: |
 | South Central US | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
 | South India | :heavy_check_mark: | :heavy_check_mark: | :x: | :heavy_check_mark: |
 | Southeast Asia | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |