Skip to content

Latest commit

 

History

History
83 lines (51 loc) · 4.05 KB

howto-configure-server-logs-portal.md

File metadata and controls

83 lines (51 loc) · 4.05 KB
title description author ms.author ms.service ms.topic ms.date
Access slow query logs - Azure portal - Azure Database for MariaDB
This article describes how to configure and access the slow query logs in Azure Database for MariaDB from the Azure portal.
ajlam
andrela
mariadb
conceptual
4/13/2020

Configure and access slow query logs from the Azure portal

You can configure, list, and download the Azure Database for MariaDB slow query logs from the Azure portal.

Prerequisites

The steps in this article require that you have Azure Database for MariaDB server.

Configure logging

Configure access to the slow query log.

  1. Sign in to the Azure portal.

  2. Select your Azure Database for MariaDB server.

  3. Under the Monitoring section in the sidebar, select Server logs. Screenshot of Server logs options

  4. To see the server parameters, select Click here to enable logs and configure log parameters.

  5. Turn slow_query_log to ON.

  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.

  7. Change any other parameters needed.

  8. Select Save.

    :::image type="content" source="./media/howto-configure-server-logs-portal/3-save-discard.png" alt-text="Screenshot of slow query log parameters and save.":::

From the Server Parameters page, you can return to the list of logs by closing the page.

View list and download logs

After logging begins, you can view a list of available slow query logs, and download individual log files.

  1. Open the Azure portal.

  2. Select your Azure Database for MariaDB server.

  3. Under the Monitoring section in the sidebar, select Server logs. The page shows a list of your log files.

    Screenshot of Server logs page, with list of logs highlighted

    [!TIP] The naming convention of the log is mysql-slow-< your server name>-yyyymmddhh.log. The date and time used in the file name is the time when the log was issued. Log files are rotated every 24 hours or 7.5 GB, whichever comes first.

  4. If needed, use the search box to quickly narrow down to a specific log, based on date and time. The search is on the name of the log.

  5. To download individual log files, select the down-arrow icon next to each log file in the table row.

    Screenshot of Server logs page, with down-arrow icon highlighted

Set up diagnostic logs

  1. Under the Monitoring section in the sidebar, select Diagnostic settings > Add diagnostic setting.

    Screenshot of Diagnostic settings options

  2. Provide a diagnostic setting name.

  3. Specify which data sinks to send the slow query logs (storage account, event hub, or Log Analytics workspace).

  4. Select MySqlSlowLogs as the log type. Screenshot of Diagnostic settings configuration options

  5. After you've configured the data sinks to pipe the slow query logs to, select Save. Screenshot of Diagnostic settings configuration options, with Save highlighted

  6. Access the slow query logs by exploring them in the data sinks you configured. It can take up to 10 minutes for the logs to appear.

Next steps

  • See Access slow query logs in CLI to learn how to download slow query logs programmatically.
  • Learn more about slow query logs in Azure Database for MariaDB.
  • For more information about the parameter definitions and logging, see the MariaDB documentation on logs.