diff --git a/docs/integrations/microsoft-azure/azure-api-management.md b/docs/integrations/microsoft-azure/azure-api-management.md index a8e8cda5d1..5651667c66 100644 --- a/docs/integrations/microsoft-azure/azure-api-management.md +++ b/docs/integrations/microsoft-azure/azure-api-management.md @@ -57,13 +57,11 @@ In this section, you will configure a pipeline for shipping diagnostic logs from 1. Use the Event Hub namespace and Event Hub name configured in the previous step in the destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
Azure API Management logs 1. Tag the location field in the source with right location value.
Azure API Management Tag Location -#### Activity Logs +#### Activity logs (optional) -To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). Do not perform this step in case you are already collecting activity logs for a subscription. +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; -:::note -Since this source contains logs from multiple regions, make sure that you do not tag this source with the location tag. -::: + ##### Enabling Microsoft Defender for Cloud diff --git a/docs/integrations/microsoft-azure/azure-app-service-environment.md b/docs/integrations/microsoft-azure/azure-app-service-environment.md index 803952dc85..3bb65d4147 100644 --- a/docs/integrations/microsoft-azure/azure-app-service-environment.md +++ b/docs/integrations/microsoft-azure/azure-app-service-environment.md @@ -48,7 +48,9 @@ In this section, you will configure a pipeline for shipping diagnostic logs from #### Activity logs (optional) -To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). If you are already collecting activity logs for a subscription, do not perform this step. +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; + + ## Installing the Azure App Service Environment app diff --git a/docs/integrations/microsoft-azure/azure-app-service-plan.md b/docs/integrations/microsoft-azure/azure-app-service-plan.md index 83fd2a1abe..924630600f 100644 --- a/docs/integrations/microsoft-azure/azure-app-service-plan.md +++ b/docs/integrations/microsoft-azure/azure-app-service-plan.md @@ -54,7 +54,9 @@ In this section, you will configure a pipeline for shipping diagnostic logs from #### Activity logs (optional) -To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). If you are already collecting activity logs for a subscription, do not perform this step. +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; + + ## Installing the Azure App Service Plan app diff --git a/docs/integrations/microsoft-azure/azure-application-gateway.md b/docs/integrations/microsoft-azure/azure-application-gateway.md index f9cf5ff96c..61afdce59d 100644 --- a/docs/integrations/microsoft-azure/azure-application-gateway.md +++ b/docs/integrations/microsoft-azure/azure-application-gateway.md @@ -69,13 +69,11 @@ Go to **Settings -> Configuration** to check your application gateway tier Application Gateway Tier Settings ::: -#### Activity Logs +#### Activity logs (optional) -To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). Do not perform this step in case you are already collecting activity logs for a subscription. +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; -:::note -Since this source contains logs from multiple regions, make sure that you do not tag this source with the location tag. -::: + ## Installing the Azure Application Gateway app diff --git a/docs/integrations/microsoft-azure/azure-cache-for-redis.md b/docs/integrations/microsoft-azure/azure-cache-for-redis.md index 198f950a3e..7283ef5990 100644 --- a/docs/integrations/microsoft-azure/azure-cache-for-redis.md +++ b/docs/integrations/microsoft-azure/azure-cache-for-redis.md @@ -59,13 +59,11 @@ In this section, you will configure a pipeline for shipping diagnostic logs from Azure Redis Cache logs 3. Tag the location field in the source with right location value.
Azure Redis Cache Tag Location -#### Activity Logs +#### Activity logs (optional) -To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). Do not perform this step if you are already collecting activity logs for a subscription. +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; -:::note -Since this source contains logs from multiple regions, ensure that you do not tag this source with the location tag. -::: + ## Installing the Azure Redis Cache app @@ -208,4 +206,4 @@ To troubleshoot metrics collection, follow the instructions in [Collect Metrics ## Additional resources - Blog: [Azure monitoring and troubleshooting](https://www.sumologic.com/blog/azure-services-monitoring) -- Glossary: [Microsoft Azure](https://www.sumologic.com/glossary/microsoft-azure) \ No newline at end of file +- Glossary: [Microsoft Azure](https://www.sumologic.com/glossary/microsoft-azure) diff --git a/docs/integrations/microsoft-azure/azure-container-instances.md b/docs/integrations/microsoft-azure/azure-container-instances.md index fa1fc269a9..b0691a0005 100644 --- a/docs/integrations/microsoft-azure/azure-container-instances.md +++ b/docs/integrations/microsoft-azure/azure-container-instances.md @@ -50,7 +50,7 @@ Use existing resource group or create a new one for deploying Azure container in Azure Storage Tag Tenant Name 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). 1. Download and update the [output_conf.yaml](https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/Azure-Container-Instances/output_conf.yaml) file with the following configurations: - * Inputs pipeline uses the [tail input plugin](https://docs.fluentbit.io/manual/pipeline/inputs/tail). Update the path parameter value with the pattern specifying a specific log file or multiple ones through the use of common wildcards. + * Inputs pipeline uses the [tail input plugin](https://docs.fluentbit.io/manual/pipeline/inputs/tail). Update the path parameter value with the pattern specifying a specific log file or multiple ones through the use of common wildcards. :::info Multiple patterns separated by commas are also allowed. ::: @@ -75,13 +75,11 @@ Use existing resource group or create a new one for deploying Azure container in - In the `imageRegistryCredentials` property, enter your image repository server, username, and password. 1. Deploy the [logging-sidecar-deploy.yaml](https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/Azure-Container-Instances/logging-sidecar-deploy.yaml) Azure template, refer to the [Azure Documentation](https://learn.microsoft.com/en-us/azure/container-instances/container-instances-multi-container-yaml#deploy-the-container-group). -#### Activity Logs +#### Activity logs (optional) -To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). Skip this step if you are already collecting activity logs for a subscription. +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; -:::note -Since this source contains logs from multiple regions, make sure that you do not tag this source with the location tag. -::: + ## Installing the Azure Container Instances app @@ -185,4 +183,3 @@ To troubleshoot metrics collection, follow the instructions in [Troubleshooting - Blog: [Azure monitoring and troubleshooting](https://www.sumologic.com/blog/azure-services-monitoring) - Blog: [How to Deploy and Manage a Container on Azure Container Service](https://www.sumologic.com/blog/how-to-deploy-and-manage-a-container-on-azure-container-service) - Glossary: [Microsoft Azure](https://www.sumologic.com/glossary/microsoft-azure) - 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 597d0496d9..c28106ed2b 100644 --- a/docs/integrations/microsoft-azure/azure-cosmos-db-for-postgresql.md +++ b/docs/integrations/microsoft-azure/azure-cosmos-db-for-postgresql.md @@ -62,13 +62,11 @@ In this section, you will configure a pipeline for shipping diagnostic logs from 4. Tag the location field in the source with right location value.
Azure Redis Cache Tag Location -#### Activity Logs +#### Activity logs (optional) -To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). Skip this step if you are already collecting activity logs for a subscription. +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; -:::note -Since this source contains logs from multiple regions, ensure that you do not tag this source with the location tag. -::: + ## Installing the Azure Cosmos DB for PostgreSQL app @@ -233,4 +231,3 @@ These alerts are metrics-based and will work for all Cosmos DB PostgreSQL instan ### HTTP Logs and Metrics Source used by Azure Functions To troubleshoot metrics collection, follow the instructions in [Collect Metrics from Azure Monitor > Troubleshooting metrics collection](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#troubleshooting-metrics-collection). - diff --git a/docs/integrations/microsoft-azure/azure-cosmos-db.md b/docs/integrations/microsoft-azure/azure-cosmos-db.md index 16ea8e5073..5fc6806530 100644 --- a/docs/integrations/microsoft-azure/azure-cosmos-db.md +++ b/docs/integrations/microsoft-azure/azure-cosmos-db.md @@ -70,11 +70,9 @@ In this section, you will configure a pipeline for shipping diagnostic logs from #### Activity logs (optional) -To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). If you are already collecting activity logs for a subscription, do not perform this step. +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; -:::note -Since this source contains logs from multiple regions, make sure that you do not tag this source with the location tag. -::: + ##### Enabling Microsoft Defender for Cloud diff --git a/docs/integrations/microsoft-azure/azure-database-for-mysql.md b/docs/integrations/microsoft-azure/azure-database-for-mysql.md index f0af1a0f6c..209744c5c8 100644 --- a/docs/integrations/microsoft-azure/azure-database-for-mysql.md +++ b/docs/integrations/microsoft-azure/azure-database-for-mysql.md @@ -83,13 +83,11 @@ In this section, you will configure a pipeline for shipping diagnostic logs from 4. Enable slow query and error logs.
Azure flexible mysql error logs 5. Tag the location field in the source with the right location value.
Azure Database for MySql Tag Location -#### Activity Logs +#### Activity logs (optional) -To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). Skip this step if you are already collecting activity logs for a subscription. +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; -:::note -Since this source contains logs from multiple regions, ensure that you do not tag this source with the location tag. -::: + ### Collecting Error Logs Error logs cannot be emitted to Azure diagnostic logs directly. To access the error logs, navigate to **Server Logs > Error Logs**, download them, then [upload the logs](/docs/send-data/hosted-collectors/http-source/logs-metrics/upload-logs) to a Sumo Logic HTTP source endpoint. Note that the HTTP source created to receive the error logs needs to be tagged with the following [fields](/docs/manage/fields/#manage-fields) with appropriate values. These values can be copied from the appropriate resource for which logs are ingested through the Azure Event Hub Source for Logs: @@ -231,4 +229,4 @@ To troubleshoot metrics collection, follow the instructions in *Collect Metrics ## Additional resources - Blog: [Azure monitoring and troubleshooting](https://www.sumologic.com/blog/azure-services-monitoring) -- Glossary: [Microsoft Azure](https://www.sumologic.com/glossary/microsoft-azure) \ No newline at end of file +- Glossary: [Microsoft Azure](https://www.sumologic.com/glossary/microsoft-azure) diff --git a/docs/integrations/microsoft-azure/azure-database-for-postgresql.md b/docs/integrations/microsoft-azure/azure-database-for-postgresql.md index 1f08feceed..5696ceee94 100644 --- a/docs/integrations/microsoft-azure/azure-database-for-postgresql.md +++ b/docs/integrations/microsoft-azure/azure-database-for-postgresql.md @@ -67,13 +67,11 @@ In this section, you will configure a pipeline for shipping diagnostic logs from 4. Tag the location field in the source with the right location value.
Azure Redis Cache Tag Location -#### Activity logs +#### Activity logs (optional) -To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). Skip this step if you are already collecting activity logs for a subscription. +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; -:::note -Since this source contains logs from multiple regions, ensure that you do not tag this source with the location tag. -::: + ## Installing the Azure Flexible Database for PostgreSQL app diff --git a/docs/integrations/microsoft-azure/azure-event-grid.md b/docs/integrations/microsoft-azure/azure-event-grid.md index 5c8b75997c..9dd3808f2a 100644 --- a/docs/integrations/microsoft-azure/azure-event-grid.md +++ b/docs/integrations/microsoft-azure/azure-event-grid.md @@ -63,13 +63,11 @@ In this section, you will configure a pipeline for shipping diagnostic logs from 1. Use the Event Hub namespace and Event Hub name configured in the previous step in the destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
Azure Event Grid logs 1. Tag the location field in the source with the right location value.
Azure Event Grid Tag Location -#### Activity Logs +#### Activity logs (optional) -To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). Do not perform this step in case you are already collecting activity logs for a subscription. +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; -:::note -Since this source contains logs from multiple regions, make sure that you do not tag this source with the location tag. -::: + ## Installing the Azure Event Grid app @@ -219,4 +217,4 @@ To troubleshoot metrics collection, follow the instructions in [Collect Metrics ## Additional resources - Blog: [Azure monitoring and troubleshooting](https://www.sumologic.com/blog/azure-services-monitoring) -- Glossary: [Microsoft Azure](https://www.sumologic.com/glossary/microsoft-azure) \ No newline at end of file +- Glossary: [Microsoft Azure](https://www.sumologic.com/glossary/microsoft-azure) diff --git a/docs/integrations/microsoft-azure/azure-event-hubs.md b/docs/integrations/microsoft-azure/azure-event-hubs.md index 11bd615c67..2068ba82d8 100644 --- a/docs/integrations/microsoft-azure/azure-event-hubs.md +++ b/docs/integrations/microsoft-azure/azure-event-hubs.md @@ -58,13 +58,11 @@ In this section, you will configure a pipeline for shipping diagnostic logs from 1. Use the Event Hub namespace and Event Hub name configured in the previous step in the destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
Azure Event Grid logs 1. Tag the location field in the source with the right location value.
Azure Virtual Machine Tag Location -#### Activity Logs +#### Activity logs (optional) -To collect activity logs, refer to the [Collecting Logs for the Azure Audit App from Event Hub](/docs/integrations/microsoft-azure/audit) section in the Azure Audit documentation. Do not perform this step in case you are already collecting activity logs for a subscription. +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; -:::note -Since this source contains logs from multiple regions, make sure that you do not tag this source with the location tag. -::: + ## Installing the Azure Event Hubs app diff --git a/docs/integrations/microsoft-azure/azure-functions.md b/docs/integrations/microsoft-azure/azure-functions.md index 8a41fa1cc7..30da5d6622 100644 --- a/docs/integrations/microsoft-azure/azure-functions.md +++ b/docs/integrations/microsoft-azure/azure-functions.md @@ -71,11 +71,9 @@ In this section, you will configure a pipeline for shipping diagnostic logs from #### Activity logs (optional) -To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). If you are already collecting activity logs for a subscription, do not perform this step. +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; -:::note -Since this source contains logs from multiple regions, make sure that you do not tag this source with the location tag. -::: + ##### Enabling Microsoft Defender for Cloud @@ -283,4 +281,4 @@ import AppUninstall from '../../reuse/apps/app-uninstall.md'; ## Additional resources - Blog: [Azure monitoring and troubleshooting](https://www.sumologic.com/blog/azure-services-monitoring) -- Glossary: [Microsoft Azure](https://www.sumologic.com/glossary/microsoft-azure) \ No newline at end of file +- Glossary: [Microsoft Azure](https://www.sumologic.com/glossary/microsoft-azure) diff --git a/docs/integrations/microsoft-azure/azure-key-vault.md b/docs/integrations/microsoft-azure/azure-key-vault.md index e5374a53e3..35190b4f7e 100644 --- a/docs/integrations/microsoft-azure/azure-key-vault.md +++ b/docs/integrations/microsoft-azure/azure-key-vault.md @@ -52,12 +52,11 @@ In this section, you will configure a pipeline for shipping diagnostic logs from 1. Use the Event Hub namespace and Event Hub name configured in the previous step in the destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
Azure Event Grid logs 1. Tag the location field in the source with the right location value.
Azure Key Vaults Tag Location -#### Activity Logs +#### Activity logs (optional) -To collect activity logs, refer to the [Collecting Logs for the Azure Audit App from Event Hub](/docs/integrations/microsoft-azure/audit) section in the Azure Audit documentation. Do not perform this step in case you are already collecting activity logs for a subscription. -:::note -Since this source contains logs from multiple regions, make sure that you do not tag this source with the location tag. -::: +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; + + ## Installing the Azure Key Vault app diff --git a/docs/integrations/microsoft-azure/azure-load-balancer.md b/docs/integrations/microsoft-azure/azure-load-balancer.md index 02ae3ad5f5..2a5ae05631 100644 --- a/docs/integrations/microsoft-azure/azure-load-balancer.md +++ b/docs/integrations/microsoft-azure/azure-load-balancer.md @@ -64,13 +64,11 @@ In this section, you will configure a pipeline for shipping diagnostic logs from Azure Load Balancer logs 3. Tag the location field in the source with the right location value.
Azure Load Balancer Tag Location -#### Activity Logs +#### Activity logs (optional) -To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). Do not perform this step if you are already collecting activity logs for a subscription. +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; -:::note -Since this source contains logs from multiple regions, ensure that you do not tag this source with the location tag. -::: + ## Installing the Azure Load Balancer app @@ -187,4 +185,4 @@ To troubleshoot metrics collection, follow the instructions in [Collect Metrics ## Additional resources - Blog: [Azure monitoring and troubleshooting](https://www.sumologic.com/blog/azure-services-monitoring) -- Glossary: [Microsoft Azure](https://www.sumologic.com/glossary/microsoft-azure) \ No newline at end of file +- Glossary: [Microsoft Azure](https://www.sumologic.com/glossary/microsoft-azure) diff --git a/docs/integrations/microsoft-azure/azure-machine-learning.md b/docs/integrations/microsoft-azure/azure-machine-learning.md index 591f9cc474..a3dc562d3d 100644 --- a/docs/integrations/microsoft-azure/azure-machine-learning.md +++ b/docs/integrations/microsoft-azure/azure-machine-learning.md @@ -50,12 +50,11 @@ In this section, you will configure a pipeline for shipping diagnostic logs from 1. Use the Event Hub namespace and Event Hub name configured in the previous step in the destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
Azure Machine Learning logs 1. Tag the location field in the source with the right location value.
Azure Machine Learning Tag Location -#### Activity Logs +#### Activity logs (optional) -To collect activity logs, refer to the [Collecting Logs for the Azure Audit App from Event Hub](/docs/integrations/microsoft-azure/audit#collecting-logs-for-the-azure-audit-app-from-event-hub) section in the Azure Audit documentation. If you're already collecting activity logs for a subscription, you can skip this step. -:::note -Since this source contains logs from multiple regions, make sure that you do not tag this source with the location tag. -::: +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; + + ## Installing the Azure Machine Learning app diff --git a/docs/integrations/microsoft-azure/azure-service-bus.md b/docs/integrations/microsoft-azure/azure-service-bus.md index f01f7337dd..d685700c49 100644 --- a/docs/integrations/microsoft-azure/azure-service-bus.md +++ b/docs/integrations/microsoft-azure/azure-service-bus.md @@ -59,13 +59,11 @@ In this section, you will configure a pipeline for shipping diagnostic logs from 1. Use the Event Hub namespace and Event Hub name configured in the previous step in the destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
Azure Service Bus logs 1. Tag the location field in the source with the right location value.
Azure Service Bus Tag Location -#### Activity Logs +#### Activity logs (optional) -To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). Do not perform this step in case you are already collecting activity logs for a subscription. +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; -:::note -Since this source contains logs from multiple regions, make sure that you do not tag this source with the location tag. -::: + ## Installing the Azure Service Bus app diff --git a/docs/integrations/microsoft-azure/azure-storage.md b/docs/integrations/microsoft-azure/azure-storage.md index ccb381244a..ab81ce27b1 100644 --- a/docs/integrations/microsoft-azure/azure-storage.md +++ b/docs/integrations/microsoft-azure/azure-storage.md @@ -89,13 +89,11 @@ In this section, you will configure a pipeline for shipping diagnostic logs from 1. Tag the location field in the source with the right location value. Azure Storage Tag Location -#### Activity Logs +#### Activity logs (optional) -To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). Do not perform this step in case you are already collecting activity logs for a subscription. +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; -:::note -Since this source contains logs from multiple regions make sure that you do not tag this source with the location tag. -::: + ##### Enabling Microsoft Defender for Cloud diff --git a/docs/integrations/microsoft-azure/azure-virtual-machine.md b/docs/integrations/microsoft-azure/azure-virtual-machine.md index cc626aa4b6..4cd6031d15 100644 --- a/docs/integrations/microsoft-azure/azure-virtual-machine.md +++ b/docs/integrations/microsoft-azure/azure-virtual-machine.md @@ -58,13 +58,11 @@ In this section, you will configure a pipeline for shipping diagnostic logs from 1. Use the Event Hub namespace and Event Hub name configured in the previous step in the destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
Azure Event Grid logs 1. Tag the location field in the source with the right location value.
Azure Virtual Machine Tag Location -#### Activity Logs +#### Activity logs (optional) -To collect activity logs, refer to the [Collecting Logs for the Azure Audit App from Event Hub](/docs/integrations/microsoft-azure/audit) section in the Azure Audit documentation. Do not perform this step in case you are already collecting activity logs for a subscription. +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; -:::note -Since this source contains logs from multiple regions, make sure that you do not tag this source with the location tag. -::: + ## Installing the Azure Virtual Machine app diff --git a/docs/integrations/microsoft-azure/azure-virtual-network.md b/docs/integrations/microsoft-azure/azure-virtual-network.md index 0adc9491dc..d77c13a9d2 100644 --- a/docs/integrations/microsoft-azure/azure-virtual-network.md +++ b/docs/integrations/microsoft-azure/azure-virtual-network.md @@ -165,13 +165,11 @@ Follow the steps detailed in the [Microsoft Azure Virtual Network documentation] If you have multiple virtual networks, you can configure virtual network flow logs using a [built-in policy](https://learn.microsoft.com/en-us/azure/network-watcher/vnet-flow-logs-policy#deploy-and-configure-virtual-network-flow-logs-using-a-built-in-policy) for each location and subscriptions. -#### Activity logs +#### Activity logs (optional) -To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). Skip this step if you are already collecting activity logs for a subscription. +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; -:::note -Since this source includes logs from multiple regions, avoid tagging it with a location tag. -::: + In order to find virtual networks without any flow log resource, you can audit flow logs configuration for virtual networks using a [built-in policy](https://learn.microsoft.com/en-us/azure/network-watcher/vnet-flow-logs-policy#audit-flow-logs-configuration-for-virtual-networks-using-a-built-in-policy). @@ -311,4 +309,3 @@ To resolve the issue, rename or delete the existing FER (AzureVirtualNetworkTarg ### HTTP Logs and Metrics Source used by Azure Functions To troubleshoot metrics collection, follow the instructions in [Collect Metrics from Azure Monitor > Troubleshooting metrics collection](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#troubleshooting-metrics-collection). - diff --git a/docs/integrations/microsoft-azure/sql.md b/docs/integrations/microsoft-azure/sql.md index 02e2002a80..5faa1e0f09 100644 --- a/docs/integrations/microsoft-azure/sql.md +++ b/docs/integrations/microsoft-azure/sql.md @@ -149,14 +149,11 @@ By default, all the tuning options are not enabled, you can enable them at the s Configure Automated Tuning -#### Activity Logs +#### Activity logs (optional) -To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). If you are already collecting activity logs for a subscription, do not perform this step. - -:::note -Since this source contains logs from multiple regions, make sure that you do not tag this source with the location tag. -::: +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; + ##### Enabling Microsoft Defender for Cloud For Security events, make sure you enable [Microsoft Defender for Cloud](https://learn.microsoft.com/en-us/azure/azure-sql/database/azure-defender-for-sql?view=azuresql#enable-microsoft-defender-for-sql). If you have an existing settings, click **Edit Settings**. @@ -523,4 +520,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 | \ No newline at end of file +| `Azure SQL - High Worker Usage` | This monitor triggers alerts when High Worker Usage is detected in Azure SQL. | Count > 60 | Count =< 60 | diff --git a/docs/integrations/microsoft-azure/web-apps.md b/docs/integrations/microsoft-azure/web-apps.md index 2dc45f26d9..d4134e8b69 100644 --- a/docs/integrations/microsoft-azure/web-apps.md +++ b/docs/integrations/microsoft-azure/web-apps.md @@ -88,11 +88,9 @@ In this section, you will configure a pipeline for shipping diagnostic logs from #### Activity logs (optional) -To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). If you are already collecting activity logs for a subscription, do not perform this step. +import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; -:::note -Since this source contains logs from multiple regions, make sure that you do not tag this source with the location tag. -::: + ##### Enabling Microsoft Defender for Cloud @@ -329,4 +327,3 @@ import AppUpdate from '../../reuse/apps/app-update.md'; import AppUninstall from '../../reuse/apps/app-uninstall.md'; - diff --git a/docs/reuse/apps/azure-activity-logs.md b/docs/reuse/apps/azure-activity-logs.md new file mode 100644 index 0000000000..9f2bbcbe09 --- /dev/null +++ b/docs/reuse/apps/azure-activity-logs.md @@ -0,0 +1,5 @@ +To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). If you are already collecting activity logs for a subscription, you can skip this step. + +:::note +Since this source includes logs from multiple regions, do not tag it with the location tag. +:::