From 4d09ef8568bba655848f742504aac0e229f3d642 Mon Sep 17 00:00:00 2001 From: Amee Lepcha Date: Wed, 13 Aug 2025 15:40:18 +0530 Subject: [PATCH 1/4] 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 a770881747293f6ec351dd92cb7ba4001bc67d76 Mon Sep 17 00:00:00 2001 From: Apoorv Kudesia Date: Wed, 13 Aug 2025 17:50:40 +0530 Subject: [PATCH 2/4] Add configure collector to Azure docs --- docs/integrations/microsoft-azure/azure-api-management.md | 4 ++++ .../microsoft-azure/azure-app-service-environment.md | 4 ++++ docs/integrations/microsoft-azure/azure-app-service-plan.md | 4 ++++ .../integrations/microsoft-azure/azure-container-instances.md | 4 ++++ .../microsoft-azure/azure-cosmos-db-for-postgresql.md | 4 ++++ docs/integrations/microsoft-azure/azure-cosmos-db.md | 4 ++++ docs/integrations/microsoft-azure/azure-database-for-mysql.md | 4 ++++ .../microsoft-azure/azure-database-for-postgresql.md | 4 ++++ docs/integrations/microsoft-azure/azure-event-grid.md | 4 ++++ docs/integrations/microsoft-azure/azure-event-hubs.md | 4 ++++ docs/integrations/microsoft-azure/azure-functions.md | 4 ++++ docs/integrations/microsoft-azure/azure-key-vault.md | 4 ++++ docs/integrations/microsoft-azure/azure-service-bus.md | 4 ++++ docs/integrations/microsoft-azure/azure-virtual-machine.md | 4 ++++ docs/integrations/microsoft-azure/azure-virtual-network.md | 4 ++++ docs/integrations/microsoft-azure/web-apps.md | 4 ++++ 16 files changed, 64 insertions(+) diff --git a/docs/integrations/microsoft-azure/azure-api-management.md b/docs/integrations/microsoft-azure/azure-api-management.md index ebed58538c..a8e8cda5d1 100644 --- a/docs/integrations/microsoft-azure/azure-api-management.md +++ b/docs/integrations/microsoft-azure/azure-api-management.md @@ -30,6 +30,10 @@ You must explicitly enable diagnostic settings for each Azure API Management ser 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/APIManagement/Logs`, `Azure/APIManagement/Metrics`. +### 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 + ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; diff --git a/docs/integrations/microsoft-azure/azure-app-service-environment.md b/docs/integrations/microsoft-azure/azure-app-service-environment.md index d165e5ed8d..803952dc85 100644 --- a/docs/integrations/microsoft-azure/azure-app-service-environment.md +++ b/docs/integrations/microsoft-azure/azure-app-service-environment.md @@ -28,6 +28,10 @@ You must explicitly enable diagnostic settings for each Azure App Service Enviro 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/AppServiceEnvironment/Logs`. +### 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 + ### Configure logs collection #### Diagnostic logs diff --git a/docs/integrations/microsoft-azure/azure-app-service-plan.md b/docs/integrations/microsoft-azure/azure-app-service-plan.md index f8553bb877..83fd2a1abe 100644 --- a/docs/integrations/microsoft-azure/azure-app-service-plan.md +++ b/docs/integrations/microsoft-azure/azure-app-service-plan.md @@ -29,6 +29,10 @@ You must explicitly enable diagnostic settings for each Azure App Service plan y 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/AppServicePlan/Logs`, `Azure/AppServicePlan/Metrics`. +### 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 + ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; diff --git a/docs/integrations/microsoft-azure/azure-container-instances.md b/docs/integrations/microsoft-azure/azure-container-instances.md index 7f03f35640..b21e641cc4 100644 --- a/docs/integrations/microsoft-azure/azure-container-instances.md +++ b/docs/integrations/microsoft-azure/azure-container-instances.md @@ -26,6 +26,10 @@ For more information on supported dimensions, refer to the [Azure documentation] * Set up application logs collection using fluent-bit sidecar container using the [http output plugin](https://docs.fluentbit.io/manual/1.5/pipeline/outputs/http) and the [tail input plugin](https://docs.fluentbit.io/manual/1.5/pipeline/inputs/tail). You must explicitly enable fluent-bit collection for each container group which you want to monitor. * Metrics collection using our [Azure Metrics Source](/docs/send-data/hosted-collectors/microsoft-source/azure-metrics-source). +### 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 + ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; diff --git a/docs/integrations/microsoft-azure/azure-cosmos-db-for-postgresql.md b/docs/integrations/microsoft-azure/azure-cosmos-db-for-postgresql.md index 53ef41e654..597d0496d9 100644 --- a/docs/integrations/microsoft-azure/azure-cosmos-db-for-postgresql.md +++ b/docs/integrations/microsoft-azure/azure-cosmos-db-for-postgresql.md @@ -30,6 +30,10 @@ You must explicitly enable diagnostic settings for each Azure Cosmos DB for Post 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/CosmosDBforPostgreSQL/Logs`, `Azure/CosmosDBforPostgreSQL/Metrics`. +### 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 + ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; diff --git a/docs/integrations/microsoft-azure/azure-cosmos-db.md b/docs/integrations/microsoft-azure/azure-cosmos-db.md index 6e51266100..16ea8e5073 100644 --- a/docs/integrations/microsoft-azure/azure-cosmos-db.md +++ b/docs/integrations/microsoft-azure/azure-cosmos-db.md @@ -46,6 +46,10 @@ You must explicitly enable diagnostic settings for each Azure Cosmos DB account 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/CosmosDB/Logs`, `Azure/CosmosDB/Metrics`. +### 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 + ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; diff --git a/docs/integrations/microsoft-azure/azure-database-for-mysql.md b/docs/integrations/microsoft-azure/azure-database-for-mysql.md index 89fb92c172..bea4e5e406 100644 --- a/docs/integrations/microsoft-azure/azure-database-for-mysql.md +++ b/docs/integrations/microsoft-azure/azure-database-for-mysql.md @@ -36,6 +36,10 @@ You must explicitly enable diagnostic settings for each Azure Database for MySQL 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/DatabaseForMySQL/Logs`, `Azure/DatabaseForMySQL/Metrics`. +### 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 + ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; diff --git a/docs/integrations/microsoft-azure/azure-database-for-postgresql.md b/docs/integrations/microsoft-azure/azure-database-for-postgresql.md index d1ef1e7b44..cd3fe95b94 100644 --- a/docs/integrations/microsoft-azure/azure-database-for-postgresql.md +++ b/docs/integrations/microsoft-azure/azure-database-for-postgresql.md @@ -32,6 +32,10 @@ You must explicitly enable diagnostic settings for each Azure Database for the P 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/DatabaseForPostgreSQL/Logs`, `Azure/DatabaseForPostgreSQL/Metrics`. +### 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 + ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; diff --git a/docs/integrations/microsoft-azure/azure-event-grid.md b/docs/integrations/microsoft-azure/azure-event-grid.md index e4fec32671..d916b2a56c 100644 --- a/docs/integrations/microsoft-azure/azure-event-grid.md +++ b/docs/integrations/microsoft-azure/azure-event-grid.md @@ -33,6 +33,10 @@ You must explicitly enable diagnostic settings for each domain, namespace, custo 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/EventGrid/Logs`, `Azure/EventGrid/Metrics`. +### 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 + ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; diff --git a/docs/integrations/microsoft-azure/azure-event-hubs.md b/docs/integrations/microsoft-azure/azure-event-hubs.md index 8bc9c3aebc..11bd615c67 100644 --- a/docs/integrations/microsoft-azure/azure-event-hubs.md +++ b/docs/integrations/microsoft-azure/azure-event-hubs.md @@ -35,6 +35,10 @@ You must explicitly enable diagnostic settings for each Event Hub Namespace you 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/EventHub/Logs`, `Azure/EventHub/Metrics`. +### 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 + ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; diff --git a/docs/integrations/microsoft-azure/azure-functions.md b/docs/integrations/microsoft-azure/azure-functions.md index 977a455fb5..4d01f44ba3 100644 --- a/docs/integrations/microsoft-azure/azure-functions.md +++ b/docs/integrations/microsoft-azure/azure-functions.md @@ -42,6 +42,10 @@ You must explicitly enable diagnostic settings for each Azure Functions you want 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/FunctionApp/Logs`, `Azure/FunctionApp/Metrics`. +### 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 + ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; diff --git a/docs/integrations/microsoft-azure/azure-key-vault.md b/docs/integrations/microsoft-azure/azure-key-vault.md index 8ef12c9cf8..e5374a53e3 100644 --- a/docs/integrations/microsoft-azure/azure-key-vault.md +++ b/docs/integrations/microsoft-azure/azure-key-vault.md @@ -31,6 +31,10 @@ You must explicitly enable diagnostic settings for each Key Vault you want to mo 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/KeyVault/Logs`, `Azure/KeyVault/Metrics`. +### 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 + ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; diff --git a/docs/integrations/microsoft-azure/azure-service-bus.md b/docs/integrations/microsoft-azure/azure-service-bus.md index 7b85e0c6da..66d73fc1a8 100644 --- a/docs/integrations/microsoft-azure/azure-service-bus.md +++ b/docs/integrations/microsoft-azure/azure-service-bus.md @@ -30,6 +30,10 @@ You must explicitly enable diagnostic settings for each Azure Service Bus namesp 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/ServiceBus/Logs`, `Azure/ServiceBus/Metrics`. +### 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 + ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; diff --git a/docs/integrations/microsoft-azure/azure-virtual-machine.md b/docs/integrations/microsoft-azure/azure-virtual-machine.md index 353c145117..cc626aa4b6 100644 --- a/docs/integrations/microsoft-azure/azure-virtual-machine.md +++ b/docs/integrations/microsoft-azure/azure-virtual-machine.md @@ -30,6 +30,10 @@ You must explicitly enable diagnostic settings for each Virtual Machine you want 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/VM/ActivityLogs`, `Azure/VM/Metrics`. +### 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 + ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; diff --git a/docs/integrations/microsoft-azure/azure-virtual-network.md b/docs/integrations/microsoft-azure/azure-virtual-network.md index bf1681ebe0..0adc9491dc 100644 --- a/docs/integrations/microsoft-azure/azure-virtual-network.md +++ b/docs/integrations/microsoft-azure/azure-virtual-network.md @@ -95,6 +95,10 @@ You must explicitly enable diagnostic settings and network flow logs for each Vi 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/VirtualNetwork/Metrics` and `Azure/VirtualNetwork/Logs`. +### 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 + ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; diff --git a/docs/integrations/microsoft-azure/web-apps.md b/docs/integrations/microsoft-azure/web-apps.md index 0dbca46c5e..2dc45f26d9 100644 --- a/docs/integrations/microsoft-azure/web-apps.md +++ b/docs/integrations/microsoft-azure/web-apps.md @@ -63,6 +63,10 @@ You must explicitly enable diagnostic settings for each web app that you want to 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/WebApps/Logs`, `Azure/WebApps/Metrics`. +### 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 + ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; From 86bd8d728b1b3908a606f6d6ace0eede76da0544 Mon Sep 17 00:00:00 2001 From: Apoorv Kudesia Date: Wed, 13 Aug 2025 17:57:28 +0530 Subject: [PATCH 3/4] update sql --- docs/integrations/microsoft-azure/sql.md | 97 ++++++++++++------------ 1 file changed, 48 insertions(+), 49 deletions(-) diff --git a/docs/integrations/microsoft-azure/sql.md b/docs/integrations/microsoft-azure/sql.md index 07246a70a1..02e2002a80 100644 --- a/docs/integrations/microsoft-azure/sql.md +++ b/docs/integrations/microsoft-azure/sql.md @@ -57,21 +57,21 @@ The Sumo Logic app for Azure SQL app uses the following log types: ```json title="Database Wait Statistics Event" { - "LogicalServerName":"npande-test-db-server", - "SubscriptionId":"c088dc46-d123-12ad-a8b7-9a123d45ad6a"",""ResourceGroup"":""npandeTestDBResGrp"",""time"":""2018-07-09T05":"13":34.520Z",""resourceId"":"/SUBSCRIPTIONS/c088dc46-d123-12ad-a8b7-9a123d45ad6a"/RESOURCEGROUPS/NPANDETESTDBRESGRP/PROVIDERS/MICROSOFT.SQL/SERVERS/NPANDE-TEST-DB-SERVER/DATABASES/NPANDETESTDB", - "category":"DatabaseWaitStatistics", - "operationName":"DatabaseWaitStatistcsEvent", - "properties":{ - "ElasticPoolName":"", - "DatabaseName":"npandeTestDB", - "start_utc_date":"2018-07-09T05:13:34.520Z", - "end_utc_date":"2018-07-09T05:18:36.050Z", - "wait_type":"WRITELOG", - "delta_max_wait_time_ms":0, - "delta_signal_wait_time_ms":0, - "delta_wait_time_ms":12, - "delta_waiting_tasks_count":2 - } + "LogicalServerName":"npande-test-db-server", + "SubscriptionId":"c088dc46-d123-12ad-a8b7-9a123d45ad6a"",""ResourceGroup"":""npandeTestDBResGrp"",""time"":""2018-07-09T05":"13":34.520Z",""resourceId"":"/SUBSCRIPTIONS/c088dc46-d123-12ad-a8b7-9a123d45ad6a"/RESOURCEGROUPS/NPANDETESTDBRESGRP/PROVIDERS/MICROSOFT.SQL/SERVERS/NPANDE-TEST-DB-SERVER/DATABASES/NPANDETESTDB", + "category":"DatabaseWaitStatistics", + "operationName":"DatabaseWaitStatistcsEvent", + "properties":{ + "ElasticPoolName":"", + "DatabaseName":"npandeTestDB", + "start_utc_date":"2018-07-09T05:13:34.520Z", + "end_utc_date":"2018-07-09T05:18:36.050Z", + "wait_type":"WRITELOG", + "delta_max_wait_time_ms":0, + "delta_signal_wait_time_ms":0, + "delta_wait_time_ms":12, + "delta_waiting_tasks_count":2 + } } ``` @@ -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 -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 +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 + +### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; @@ -112,30 +114,27 @@ 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. - * 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 + * 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 +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. 1. To enable the Audit logs in Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-sql/database/auditing-setup?view=azuresql#configure-auditing-for-your-server). Perform below steps for each Azure SQL database that you want to monitor. - * Choose `Event Hub` as the destination. Refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-sql/database/auditing-setup?view=azuresql#audit-to-event-hubs-destination). - * Use the same Event hub namespace and Event hub name as configured in `Diagnostic logs` in destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
Configure Auditing + * Choose `Event Hub` as the destination. Refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-sql/database/auditing-setup?view=azuresql#audit-to-event-hubs-destination). + * Use the same Event hub namespace and Event hub name as configured in `Diagnostic logs` in destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
Configure Auditing 1. By default, auditing is enabled only for the below action groups. Refer to [Azure help](https://learn.microsoft.com/en-us/sql/relational-databases/security/auditing/sql-server-audit-action-groups-and-actions) for more details on supported action groups and actions. - * "SUCCESSFUL_DATABASE_AUTHENTICATION_GROUP" - * "FAILED_DATABASE_AUTHENTICATION_GROUP" - * "BATCH_COMPLETED_GROUP" + * "SUCCESSFUL_DATABASE_AUTHENTICATION_GROUP" + * "FAILED_DATABASE_AUTHENTICATION_GROUP" + * "BATCH_COMPLETED_GROUP" Follow the below command to update the audit policy with new actions using Azure CLI. If you want to use any other mechanism, refer to the [Microsoft documentation](https://learn.microsoft.com/en-us/sql/relational-databases/security/auditing/create-a-server-audit-and-database-audit-specification?view=sql-server-ver16). ). @@ -389,7 +388,7 @@ For more information about the statistics presented on the QueryStoreWaitStats d **Wait Category Trend.** A stacked column chart that shows the count of wait events by category per timeslice over the last 24 hours. -**Total Wait Time for Query by Wait Category**. A stacked column chart that shows, for each query, the length of time a query spent waiting in each Wait Category over the last 24 hours. +**Total Wait Time for Query by Wait Category**. A stacked column chart that shows, for each query, the length of time a query spent waiting in each Wait Category over the last 24 hours. **Wait Details**. The table displays wait statistics as encountered by queries on a given database, residing on a given logical server in the last 24 hours. @@ -424,7 +423,7 @@ For more information about the data presented on the Timeouts dashboard, see [Ti Timeouts -**Timeouts**. The count of timeouts over the last 7 days. +**Timeouts**. The count of timeouts over the last 7 days. **Top 10 Error States**. A table that lists the top 10 errors states that have occurred over the last 7 days and the count of errors in each state. @@ -437,8 +436,8 @@ For more information about the data presented on the Timeouts dashboard, see [Ti The **Azure SQL - Health** dashboard provides information of any service health incidents or resource health events associated with SQL database service or resource in your azure account. Use this dashboard to: - * View recent resource and service health incidents. - * View distribution of service and resource health by incident type. +* View recent resource and service health incidents. +* View distribution of service and resource health by incident type. Azure SQL health dashboard @@ -448,11 +447,11 @@ Use this dashboard to: The **Azure SQL - Policy and Recommendations** dashboard provides information of all effect action operations performed by Azure Policy and recommendations events from Azure Advisor. Use this dashboard to: - * Monitor policy events with warnings and errors. - * View recent failed policy events. - * View total recommendation events. - * Identify High Impact recommendations. - * View recent recommendation events and navigate to the affected resource. +* Monitor policy events with warnings and errors. +* View recent failed policy events. +* View total recommendation events. +* Identify High Impact recommendations. +* View recent recommendation events and navigate to the affected resource. Azure SQL - Policy and Recommendations dashboard @@ -462,9 +461,9 @@ Use this dashboard to: The **Azure SQL - Administrative Operations** dashboard provides details on read/write/delete specific changes, different operations used, top 10 operations that caused most errors, and users performing admin operations. Use this dashboard to: - * Identify top users performing administrative operations. - * View Top 10 operations that caused the most errors. - * View recent read, write, and delete operations. +* Identify top users performing administrative operations. +* View Top 10 operations that caused the most errors. +* View recent read, write, and delete operations. Azure SQL Administrative Operations dashboard @@ -473,9 +472,9 @@ Use this dashboard to: The **Azure SQL - SQL Security Audit** dashboard provides audit information on server level events and database level events including DML and DDL statements executed. Use this dashboard to: - * Identify failed login and their geo locations. - * View recent DDL, DML, DQL, and TCL statements. - * Track who (host name, service principal, ip address) and what (object, database, server) information associated with any database operation. +* Identify failed login and their geo locations. +* View recent DDL, DML, DQL, and TCL statements. +* Track who (host name, service principal, ip address) and what (object, database, server) information associated with any database operation. Azure SQL Security Audit dashboard @@ -485,9 +484,9 @@ Use this dashboard to: The **Azure SQL - Automatic Tuning** dashboard provides information about automatic tuning recommendations for a database. Use this dashboard to: - * View recent changes in tuning configuration. - * View create index recommendations. - * View drop index recommendations. +* View recent changes in tuning configuration. +* View create index recommendations. +* View drop index recommendations. Azure SQL Automated Tuning dashboard @@ -524,4 +523,4 @@ These alerts are metrics-based and will work for Azure SQL. | `Azure SQL - Data IO percentage` | This monitor triggers alerts when High Data IO percentage is detected in Azure SQL. | Count > 90 | Count =< 90 | | `Azure SQL - DTU Percentage` | This monitor triggers alerts when High average DTU consumption percentage is detected in Azure SQL. | Count > 80 | Count =< 80 | | `Azure SQL - Tempdb Percent Log Used` | This monitor triggers alerts when High Tempdb Percent Log Usage is detected in Azure SQL. | Count > 60 | Count =< 60 | -| `Azure SQL - High Worker Usage` | This monitor triggers alerts when High Worker Usage is detected in Azure SQL. | Count > 60 | Count =< 60 | +| `Azure SQL - High Worker Usage` | This monitor triggers alerts when High Worker Usage is detected in Azure SQL. | Count > 60 | Count =< 60 | \ No newline at end of file From 48c35970a4c69197d41c4ed6d0717b4b36c17bfb Mon Sep 17 00:00:00 2001 From: Apoorv Kudesia Date: Wed, 13 Aug 2025 18:24:20 +0530 Subject: [PATCH 4/4] update add more apps --- .../integrations/microsoft-azure/azure-application-gateway.md | 4 ++++ docs/integrations/microsoft-azure/azure-cache-for-redis.md | 4 ++++ docs/integrations/microsoft-azure/azure-load-balancer.md | 4 ++++ docs/integrations/microsoft-azure/azure-storage.md | 4 ++++ 4 files changed, 16 insertions(+) diff --git a/docs/integrations/microsoft-azure/azure-application-gateway.md b/docs/integrations/microsoft-azure/azure-application-gateway.md index 7b0b557245..f9cf5ff96c 100644 --- a/docs/integrations/microsoft-azure/azure-application-gateway.md +++ b/docs/integrations/microsoft-azure/azure-application-gateway.md @@ -40,6 +40,10 @@ You must explicitly enable diagnostic settings for each Azure Application Gatewa 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/ApplicationGateway/Logs`, `Azure/ApplicationGateway/Metrics`. +### 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 + ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; diff --git a/docs/integrations/microsoft-azure/azure-cache-for-redis.md b/docs/integrations/microsoft-azure/azure-cache-for-redis.md index ae4391fa09..5e90150665 100644 --- a/docs/integrations/microsoft-azure/azure-cache-for-redis.md +++ b/docs/integrations/microsoft-azure/azure-cache-for-redis.md @@ -30,6 +30,10 @@ You must explicitly enable diagnostic settings for each Azure Cache for Redis yo 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/RedisCache/Logs` and `Azure/RedisCache/Metrics`. +### 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 + ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; diff --git a/docs/integrations/microsoft-azure/azure-load-balancer.md b/docs/integrations/microsoft-azure/azure-load-balancer.md index 3e512c9d08..9c5f255a2a 100644 --- a/docs/integrations/microsoft-azure/azure-load-balancer.md +++ b/docs/integrations/microsoft-azure/azure-load-balancer.md @@ -33,6 +33,10 @@ You must explicitly enable diagnostic settings for each Load Balancer you want t 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/LoadBalancer/Logs` and `Azure/LoadBalancer/Metrics`. +### 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 + ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; diff --git a/docs/integrations/microsoft-azure/azure-storage.md b/docs/integrations/microsoft-azure/azure-storage.md index b01daae913..ccb381244a 100644 --- a/docs/integrations/microsoft-azure/azure-storage.md +++ b/docs/integrations/microsoft-azure/azure-storage.md @@ -65,6 +65,10 @@ You must explicitly enable diagnostic settings for each storage service (blob, q 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/Storage/Logs`, `Azure/Storage/Metrics`. +### 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 + ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md';