Skip to content

Commit 4510983

Browse files
authored
Merge pull request #102598 from ajlam/master
Remove logging pricing tier limitation
2 parents f9fa94c + f6ece40 commit 4510983

File tree

2 files changed

+2
-8
lines changed

2 files changed

+2
-8
lines changed

articles/mariadb/concepts-server-logs.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ajlam
55
ms.author: andrela
66
ms.service: mariadb
77
ms.topic: conceptual
8-
ms.date: 01/21/2020
8+
ms.date: 01/28/2020
99
---
1010
# Slow query logs in Azure Database for MariaDB
1111
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.
@@ -46,9 +46,6 @@ See the MariaDB [slow query log documentation](https://mariadb.com/kb/en/library
4646
## Diagnostic logs
4747
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).
4848

49-
> [!IMPORTANT]
50-
> This diagnostic feature for server logs is only available in the General Purpose and Memory Optimized [pricing tiers](concepts-pricing-tiers.md).
51-
5249
The following table describes what's in each log. Depending on the output method, the fields included and the order in which they appear may vary.
5350

5451
| **Property** | **Description** |

articles/mysql/concepts-server-logs.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ajlam
55
ms.author: andrela
66
ms.service: mysql
77
ms.topic: conceptual
8-
ms.date: 01/21/2020
8+
ms.date: 01/28/2020
99
---
1010
# Slow query logs in Azure Database for MySQL
1111
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.
@@ -46,9 +46,6 @@ See the MySQL [slow query log documentation](https://dev.mysql.com/doc/refman/5.
4646
## Diagnostic logs
4747
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).
4848

49-
> [!IMPORTANT]
50-
> This diagnostic feature for server logs is only available in the General Purpose and Memory Optimized [pricing tiers](concepts-pricing-tiers.md).
51-
5249
The following table describes what's in each log. Depending on the output method, the fields included and the order in which they appear may vary.
5350

5451
| **Property** | **Description** |

0 commit comments

Comments
 (0)