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/mariadb/concepts-server-logs.md
+20-16Lines changed: 20 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,29 +5,15 @@ author: ajlam
5
5
ms.author: andrela
6
6
ms.service: mariadb
7
7
ms.topic: conceptual
8
-
ms.date: 3/18/2020
8
+
ms.date: 4/13/2020
9
9
---
10
10
# Slow query logs in Azure Database for MariaDB
11
11
In Azure Database for MariaDB, the slow query log is available to users. Access to the transaction log is not supported. The slow query log can be used to identify performance bottlenecks for troubleshooting.
12
12
13
13
For more information about the slow query log, see the MariaDB documentation for [slow query log](https://mariadb.com/kb/en/library/slow-query-log-overview/).
14
14
15
-
## Access slow query logs
16
-
You can list and download Azure Database for MariaDB slow query logs using the Azure portal, and the Azure CLI.
17
-
18
-
In the Azure portal, select your Azure Database for MariaDB server. Under the **Monitoring** heading, select the **Server Logs** page.
19
-
20
-
For more information on Azure CLI, see [Configure and access server logs using Azure CLI](howto-configure-server-logs-cli.md).
21
-
22
-
Similarly, you can pipe the logs to Azure Monitor using Diagnostic Logs. See [below](concepts-server-logs.md#diagnostic-logs) for more information.
23
-
24
-
## Log retention
25
-
Logs are available for 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.
26
-
27
-
Logs are rotated every 24 hours or 7 GB, whichever comes first.
28
-
29
15
## Configure slow query logging
30
-
By default the slow query log is disabled. To enable it, set slow_query_log to ON.
16
+
By default the slow query log is disabled. To enable it, set `slow_query_log` to ON. This can be enabled using the Azure portal or Azure CLI.
31
17
32
18
Other parameters you can adjust include:
33
19
@@ -43,6 +29,21 @@ Other parameters you can adjust include:
43
29
44
30
See the MariaDB [slow query log documentation](https://mariadb.com/kb/en/library/slow-query-log-overview/) for full descriptions of the slow query log parameters.
45
31
32
+
## Access slow query logs
33
+
There are two options for accessing slow query logs in Azure Database for MariaDB: local server storage or Azure Monitor Diagnostic Logs. This is set using the `log_output` parameter.
34
+
35
+
For local server storage, you can list and download slow query logs using the Azure portal or the Azure CLI. In the Azure portal, navigate to your server in the Azure portal. Under the **Monitoring** heading, select the **Server Logs** page. For more information on Azure CLI, see [Configure and access server logs using Azure CLI](howto-configure-server-logs-cli.md).
36
+
37
+
Azure Monitor Diagnostic Logs allows you to pipe slow query logs to Azure Monitor Logs (Log Analytics), Azure Storage, or Event Hubs. See [below](concepts-server-logs.md#diagnostic-logs) for more information.
38
+
39
+
## Local server storage log retention
40
+
When logging to the server's local storage, logs are available for 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.
41
+
42
+
Logs are rotated every 24 hours or 7 GB, whichever comes first.
43
+
44
+
> [!Note]
45
+
> The above log retention does not apply to logs that are piped using Azure Monitor Diagnostic Logs. You can change the retention period for the data sinks being emitted to (ex. Azure Storage).
46
+
46
47
## Diagnostic logs
47
48
Azure Database for MariaDB is integrated with Azure Monitor Diagnostic Logs. Once you have enabled slow query logs on your MariaDB server, you can choose to have them emitted to Azure Monitor logs, Event Hubs, or Azure Storage. To learn more about how to enable diagnostic logs, see the how to section of the [diagnostic logs documentation](../azure-monitor/platform/platform-logs-overview.md).
48
49
@@ -76,6 +77,9 @@ The following table describes what's in each log. Depending on the output method
76
77
|`thread_id_s`| Thread ID |
77
78
|`\_ResourceId`| Resource URI |
78
79
80
+
> [!Note]
81
+
> For `sql_text`, log will be truncated if it exceeds 2048 characters.
82
+
79
83
## Analyze logs in Azure Monitor Logs
80
84
81
85
Once your slow query logs are piped to Azure Monitor Logs through Diagnostic Logs, you can perform further analysis of your slow queries. Below are some sample queries to help you get started. Make sure to update the below with your server name.
Copy file name to clipboardExpand all lines: articles/mariadb/howto-configure-server-logs-cli.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: andrela
6
6
ms.service: mariadb
7
7
ms.devlang: azurecli
8
8
ms.topic: conceptual
9
-
ms.date: 3/18/2020
9
+
ms.date: 4/13/2020
10
10
---
11
11
# Configure and access slow query logs by using Azure CLI
12
12
You can download the Azure Database for MariaDB slow query logs by using Azure CLI, the Azure command-line utility.
@@ -16,30 +16,32 @@ To step through this how-to guide, you need:
16
16
-[Azure Database for MariaDB server](quickstart-create-mariadb-server-database-using-azure-cli.md)
17
17
- The [Azure CLI](/cli/azure/install-azure-cli) or Azure Cloud Shell in the browser
18
18
19
-
## Configure logging for Azure Database for MariaDB
20
-
You can configure the server to access the MariaDB slow query log by taking the following steps:
21
-
1. Turn on logging by setting the **slow\_query\_log** parameter to ON.
22
-
2. Adjust other parameters, such as **long\_query\_time** and **log\_slow\_admin\_statements**.
19
+
## Configure logging
20
+
You can configure the server to access the MySQL slow query log by taking the following steps:
21
+
1. Turn on slow query logging by setting the **slow\_query\_log** parameter to ON.
22
+
2. Select where to output the logs to using **log\_output**. To send logs to both local storage and Azure Monitor Diagnostic Logs, select **File**. To send logs only to Azure Monitor Logs, select **None**
23
+
3. Adjust other parameters, such as **long\_query\_time** and **log\_slow\_admin\_statements**.
23
24
24
25
To learn how to set the value of these parameters through Azure CLI, see [How to configure server parameters](howto-configure-server-parameters-cli.md).
25
26
26
27
For example, the following CLI command turns on the slow query log, sets the long query time to 10 seconds, and then turns off the logging of the slow admin statement. Finally, it lists the configuration options for your review.
27
28
```azurecli-interactive
28
29
az mariadb server configuration set --name slow_query_log --resource-group myresourcegroup --server mydemoserver --value ON
30
+
az mariadb server configuration set --name log_output --resource-group myresourcegroup --server mydemoserver --value FILE
29
31
az mariadb server configuration set --name long_query_time --resource-group myresourcegroup --server mydemoserver --value 10
30
32
az mariadb server configuration set --name log_slow_admin_statements --resource-group myresourcegroup --server mydemoserver --value OFF
31
33
az mariadb server configuration list --resource-group myresourcegroup --server mydemoserver
32
34
```
33
35
34
36
## List logs for Azure Database for MariaDB server
35
-
To list the available slow query log files for your server, run the [az mariadb server-logs list](/cli/azure/mariadb/server-logs#az-mariadb-server-logs-list) command.
37
+
If **log_output** is configured to "File", you can access logs directly from the server's local storage. To list the available slow query log files for your server, run the [az mariadb server-logs list](/cli/azure/mariadb/server-logs#az-mariadb-server-logs-list) command.
36
38
37
39
You can list the log files for server **mydemoserver.mariadb.database.azure.com** under the resource group **myresourcegroup**. Then direct the list of log files to a text file called **log\_files\_list.txt**.
38
40
```azurecli-interactive
39
41
az mariadb server-logs list --resource-group myresourcegroup --server mydemoserver > log_files_list.txt
40
42
```
41
43
## Download logs from the server
42
-
With the [az mariadb server-logs download](/cli/azure/mariadb/server-logs#az-mariadb-server-logs-download) command, you can download individual log files for your server.
44
+
If **log_output** is configured to "File", you can download individual log files from your server with the [az mariadb server-logs download](/cli/azure/mariadb/server-logs#az-mariadb-server-logs-download) command.
43
45
44
46
Use the following example to download the specific log file for the server **mydemoserver.mariadb.database.azure.com** under the resource group **myresourcegroup** to your local environment.
Copy file name to clipboardExpand all lines: articles/mariadb/howto-configure-server-logs-portal.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: ajlam
5
5
ms.author: andrela
6
6
ms.service: mariadb
7
7
ms.topic: conceptual
8
-
ms.date: 3/18/2020
8
+
ms.date: 4/13/2020
9
9
---
10
10
11
11
# Configure and access slow query logs from the Azure portal
@@ -27,11 +27,15 @@ Configure access to the slow query log.
27
27
28
28
4. To see the server parameters, select **Click here to enable logs and configure log parameters**.
29
29
30
-
5.Change the parameters that you need to adjust, including turning **slow_query_log** to **ON**. All changes you make in this session are highlighted in purple.
30
+
5.Turn **slow_query_log** to **ON**.
31
31
32
-
After you have changed the parameters, select **Save**. Or, you can discard your changes.
32
+
6. Select where to output the logs to using **log_output**. To send logs to both local storage and Azure Monitor Diagnostic Logs, select **File**.
33
33
34
-
34
+
7. Change any other parameters needed.
35
+
36
+
8. Select **Save**.
37
+
38
+
:::image type="content" source="./media/howto-configure-server-logs-portal/3-save-discard.png" alt-text="Screenshot of slow query log parameters and save.":::
35
39
36
40
From the **Server Parameters** page, you can return to the list of logs by closing the page.
Copy file name to clipboardExpand all lines: articles/mysql/concepts-server-logs.md
+17-16Lines changed: 17 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,29 +5,15 @@ author: ajlam
5
5
ms.author: andrela
6
6
ms.service: mysql
7
7
ms.topic: conceptual
8
-
ms.date: 01/28/2020
8
+
ms.date: 4/13/2020
9
9
---
10
10
# Slow query logs in Azure Database for MySQL
11
11
In Azure Database for MySQL, the slow query log is available to users. Access to the transaction log is not supported. The slow query log can be used to identify performance bottlenecks for troubleshooting.
12
12
13
13
For more information about the MySQL slow query log, see the MySQL reference manual's [slow query log section](https://dev.mysql.com/doc/refman/5.7/en/slow-query-log.html).
14
14
15
-
## Access slow query logs
16
-
You can list and download Azure Database for MySQL slow query logs using the Azure portal, and the Azure CLI.
17
-
18
-
In the Azure portal, select your Azure Database for MySQL server. Under the **Monitoring** heading, select the **Server Logs** page.
19
-
20
-
For more information on Azure CLI, see [Configure and access slow query logs using Azure CLI](howto-configure-server-logs-in-cli.md).
21
-
22
-
Similarly, you can pipe the logs to Azure Monitor using Diagnostic Logs. See [below](concepts-server-logs.md#diagnostic-logs) for more information.
23
-
24
-
## Log retention
25
-
Logs are available for 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.
26
-
27
-
Logs are rotated every 24 hours or 7 GB, whichever comes first.
28
-
29
15
## Configure slow query logging
30
-
By default the slow query log is disabled. To enable it, set slow_query_log to ON.
16
+
By default the slow query log is disabled. To enable it, set `slow_query_log` to ON. This can be enabled using the Azure portal or Azure CLI.
31
17
32
18
Other parameters you can adjust include:
33
19
@@ -43,6 +29,21 @@ Other parameters you can adjust include:
43
29
44
30
See the MySQL [slow query log documentation](https://dev.mysql.com/doc/refman/5.7/en/slow-query-log.html) for full descriptions of the slow query log parameters.
45
31
32
+
## Access slow query logs
33
+
There are two options for accessing slow query logs in Azure Database for MySQL: local server storage or Azure Monitor Diagnostic Logs. This is set using the `log_output` parameter.
34
+
35
+
For local server storage, you can list and download slow query logs using the Azure portal or the Azure CLI. In the Azure portal, navigate to your server in the Azure portal. Under the **Monitoring** heading, select the **Server Logs** page. For more information on Azure CLI, see [Configure and access slow query logs using Azure CLI](howto-configure-server-logs-in-cli.md).
36
+
37
+
Azure Monitor Diagnostic Logs allows you to pipe slow query logs to Azure Monitor Logs (Log Analytics), Azure Storage, or Event Hubs. See [below](concepts-server-logs.md#diagnostic-logs) for more information.
38
+
39
+
## Local server storage log retention
40
+
When logging to the server's local storage, logs are available for 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.
41
+
42
+
Logs are rotated every 24 hours or 7 GB, whichever comes first.
43
+
44
+
> [!Note]
45
+
> The above log retention does not apply to logs that are piped using Azure Monitor Diagnostic Logs. You can change the retention period for the data sinks being emitted to (ex. Azure Storage).
46
+
46
47
## Diagnostic logs
47
48
Azure Database for MySQL is integrated with Azure Monitor Diagnostic Logs. Once you have enabled slow query logs on your MySQL server, you can choose to have them emitted to Azure Monitor logs, Event Hubs, or Azure Storage. To learn more about how to enable diagnostic logs, see the how to section of the [diagnostic logs documentation](../azure-monitor/platform/platform-logs-overview.md).
Copy file name to clipboardExpand all lines: articles/mysql/howto-configure-server-logs-in-cli.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: andrela
6
6
ms.service: mysql
7
7
ms.devlang: azurecli
8
8
ms.topic: conceptual
9
-
ms.date: 3/18/2020
9
+
ms.date: 4/13/2020
10
10
---
11
11
# Configure and access slow query logs by using Azure CLI
12
12
You can download the Azure Database for MySQL slow query logs by using Azure CLI, the Azure command-line utility.
@@ -19,27 +19,29 @@ To step through this how-to guide, you need:
19
19
## Configure logging
20
20
You can configure the server to access the MySQL slow query log by taking the following steps:
21
21
1. Turn on slow query logging by setting the **slow\_query\_log** parameter to ON.
22
-
2. Adjust other parameters, such as **long\_query\_time** and **log\_slow\_admin\_statements**.
22
+
2. Select where to output the logs to using **log\_output**. To send logs to both local storage and Azure Monitor Diagnostic Logs, select **File**. To send logs only to Azure Monitor Logs, select **None**
23
+
3. Adjust other parameters, such as **long\_query\_time** and **log\_slow\_admin\_statements**.
23
24
24
25
To learn how to set the value of these parameters through Azure CLI, see [How to configure server parameters](howto-configure-server-parameters-using-cli.md).
25
26
26
27
For example, the following CLI command turns on the slow query log, sets the long query time to 10 seconds, and then turns off the logging of the slow admin statement. Finally, it lists the configuration options for your review.
27
28
```azurecli-interactive
28
29
az mysql server configuration set --name slow_query_log --resource-group myresourcegroup --server mydemoserver --value ON
30
+
az mysql server configuration set --name log_output --resource-group myresourcegroup --server mydemoserver --value FILE
29
31
az mysql server configuration set --name long_query_time --resource-group myresourcegroup --server mydemoserver --value 10
30
32
az mysql server configuration set --name log_slow_admin_statements --resource-group myresourcegroup --server mydemoserver --value OFF
31
33
az mysql server configuration list --resource-group myresourcegroup --server mydemoserver
32
34
```
33
35
34
36
## List logs for Azure Database for MySQL server
35
-
To list the available slow query log files for your server, run the [az mysql server-logs list](/cli/azure/mysql/server-logs#az-mysql-server-logs-list) command.
37
+
If **log_output** is configured to "File", you can access logs directly from the server's local storage. To list the available slow query log files for your server, run the [az mysql server-logs list](/cli/azure/mysql/server-logs#az-mysql-server-logs-list) command.
36
38
37
39
You can list the log files for server **mydemoserver.mysql.database.azure.com** under the resource group **myresourcegroup**. Then direct the list of log files to a text file called **log\_files\_list.txt**.
38
40
```azurecli-interactive
39
41
az mysql server-logs list --resource-group myresourcegroup --server mydemoserver > log_files_list.txt
40
42
```
41
43
## Download logs from the server
42
-
With the [az mysql server-logs download](/cli/azure/mysql/server-logs#az-mysql-server-logs-download) command, you can download individual log files for your server.
44
+
If **log_output** is configured to "File", you can download individual log files from your server with the [az mysql server-logs download](/cli/azure/mysql/server-logs#az-mysql-server-logs-download) command.
43
45
44
46
Use the following example to download the specific log file for the server **mydemoserver.mysql.database.azure.com** under the resource group **myresourcegroup** to your local environment.
0 commit comments