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: docs/integrations/microsoft-azure/azure-database-for-mariadb.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ In this section, you will configure a pipeline for shipping metrics from Azure M
36
36
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" />
37
37
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).
38
38
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.
40
40
* Choose `Stream to an event hub` as destination.
41
41
* Select `AllMetrics`.
42
42
* 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
47
47
48
48
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).
49
49
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.
51
51
* Choose `Stream to an event hub` as the destination.
52
52
* Select `MySqlSlowLogs` and `MySqlAuditLogs`.
53
53
* 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