Skip to content

Commit f0a3212

Browse files
authored
Update azure-database-for-mariadb.md
1 parent c248c4e commit f0a3212

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/integrations/microsoft-azure/azure-database-for-mariadb.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ In this section, you will configure a pipeline for shipping metrics from Azure M
3636
1. Create a hosted collector and tag the `tenant_name` field. You can get the tenant name using the instructions [here](https://learn.microsoft.com/en-us/azure/active-directory-b2c/tenant-management-read-tenant-name#get-your-tenant-name). <br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Storage-Tag-Tenant-Name.png')} alt="Azure Tag Tenant Name" style={{border: '1px solid gray'}} width="500" />
3737
1. [Configure an HTTP Source](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-1-configure-an-http-source).
3838
1. [Configure and deploy the ARM Template](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-2-configure-azure-resources-using-arm-template).
39-
1. [Export metrics to Event Hub](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-3-export-metrics-for-a-particular-resource-to-event-hub). Perform below steps for each Azure Database for MariaDB server that you want to monitor.
39+
1. [Export metrics to Event Hub](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-3-export-metrics-for-a-particular-resource-to-event-hub). Perform the steps below for each Azure Database for MariaDB server that you want to monitor.
4040
* Choose `Stream to an event hub` as destination.
4141
* Select `AllMetrics`.
4242
* Use the Event hub namespace created by the ARM template in Step 2 above. You can create a new Event hub or use the one created by ARM template. You can use the default policy `RootManageSharedAccessKey` as the policy name.
@@ -47,7 +47,7 @@ In this section, you will configure a pipeline for shipping diagnostic logs from
4747

4848
1. To enable slow query logs, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/mariadb/concepts-server-logs#configure-slow-query-logging).
4949
2. To set up the Azure Event Hubs source in Sumo Logic, refer to [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/).
50-
3. To create the Diagnostic settings in Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/mariadb/howto-configure-server-logs-portal#set-up-diagnostic-logs). Perform below steps for each Azure Database for MariaDB server that you want to monitor.
50+
3. To create the Diagnostic settings in Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/mariadb/howto-configure-server-logs-portal#set-up-diagnostic-logs). Perform the steps below for each Azure Database for MariaDB server that you want to monitor.
5151
* Choose `Stream to an event hub` as the destination.
5252
* Select `MySqlSlowLogs` and `MySqlAuditLogs`.
5353
* Use the Event hub namespace and Event hub name configured in previous step in destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.

0 commit comments

Comments
 (0)