From 4d09ef8568bba655848f742504aac0e229f3d642 Mon Sep 17 00:00:00 2001 From: Amee Lepcha Date: Wed, 13 Aug 2025 15:40:18 +0530 Subject: [PATCH 1/3] Update sql.md --- docs/integrations/microsoft-azure/sql.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/integrations/microsoft-azure/sql.md b/docs/integrations/microsoft-azure/sql.md index e459128e00..07246a70a1 100644 --- a/docs/integrations/microsoft-azure/sql.md +++ b/docs/integrations/microsoft-azure/sql.md @@ -100,19 +100,21 @@ When you configure the event hubs source or HTTP source, plan your source catego ### Configure metrics collection +1. Create a hosted collector if not already configured 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).
Azure Tag Tenant Name + import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; ### Configure logs collection - #### Diagnostic logs In this section, you will configure a pipeline for shipping diagnostic logs from [Azure Monitor](https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-get-started) to an Event Hub. +1. Create a hosted collector if not already configured 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).
Azure Tag Tenant Name 1. To set up the Azure Event Hubs source in Sumo Logic, refer to the [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/). -2. To create the Diagnostic settings in Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-gb/azure/data-factory/monitor-configure-diagnostics). Perform below steps for each Azure SQL database that you want to monitor. +1. To create the Diagnostic settings in Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-gb/azure/data-factory/monitor-configure-diagnostics). Perform below steps for each Azure SQL database that you want to monitor. * Choose `Stream to an event hub` as the destination. * Select all the log types except `SQL Security Audit Event`. * 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. From 2b6aa9d1678b4560ff4654d913da4d39127d98a4 Mon Sep 17 00:00:00 2001 From: Jagadisha V Date: Wed, 13 Aug 2025 16:17:04 +0530 Subject: [PATCH 2/3] update the sql doc --- docs/integrations/microsoft-azure/sql.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/integrations/microsoft-azure/sql.md b/docs/integrations/microsoft-azure/sql.md index 07246a70a1..cd77881f54 100644 --- a/docs/integrations/microsoft-azure/sql.md +++ b/docs/integrations/microsoft-azure/sql.md @@ -98,9 +98,11 @@ You must explicitly enable diagnostic settings for each Azure SQL database that When you configure the event hubs source or HTTP source, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example: `Azure/SQL/Logs`, `Azure/SQL/ActivityLogs`, and `Azure/SQL/Metrics`. -### Configure metrics collection +### Configure collector + +Create a hosted collector if not already configured 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). Make sure you create the required sources in this collector.
Azure Tag Tenant Name -1. Create a hosted collector if not already configured 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).
Azure Tag Tenant Name +### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; @@ -112,7 +114,6 @@ import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; In this section, you will configure a pipeline for shipping diagnostic logs from [Azure Monitor](https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-get-started) to an Event Hub. -1. Create a hosted collector if not already configured 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).
Azure Tag Tenant Name 1. To set up the Azure Event Hubs source in Sumo Logic, refer to the [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/). 1. To create the Diagnostic settings in Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-gb/azure/data-factory/monitor-configure-diagnostics). Perform below steps for each Azure SQL database that you want to monitor. * Choose `Stream to an event hub` as the destination. From 7dd8a293f766abc2da1818073b5d4455149deba5 Mon Sep 17 00:00:00 2001 From: Jagadisha V Date: Wed, 13 Aug 2025 16:18:55 +0530 Subject: [PATCH 3/3] minor formatting --- docs/integrations/microsoft-azure/sql.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/docs/integrations/microsoft-azure/sql.md b/docs/integrations/microsoft-azure/sql.md index cd77881f54..f5f7368132 100644 --- a/docs/integrations/microsoft-azure/sql.md +++ b/docs/integrations/microsoft-azure/sql.md @@ -118,15 +118,13 @@ In this section, you will configure a pipeline for shipping diagnostic logs from 1. To create the Diagnostic settings in Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-gb/azure/data-factory/monitor-configure-diagnostics). Perform below steps for each Azure SQL database that you want to monitor. * Choose `Stream to an event hub` as the destination. * Select all the log types except `SQL Security Audit Event`. - * 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. - - Azure Database for MySql Tag Location - -3. Tag the location field in the source with right location value.
Azure Database for MySql Tag Location + * 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.
Azure Database for MySql Tag Location +1. Tag the location field in the source with right location value.
Azure Database for MySql Tag Location :::note Auto Tuning logs will be collected when Auto Tuning feature is enabled in Azure SQL. Click [here](https://learn.microsoft.com/en-us/azure/azure-sql/database/automatic-tuning-enable?view=azuresql) to learn more on how to enable this feature. ::: + #### Enable SQL Security Audit logs In this section, you will configure a pipeline for shipping diagnostic logs from [Azure Monitor](https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-get-started) to an Event Hub.