From 48a509944031b095bc9f95b8ff71144ff50632ac Mon Sep 17 00:00:00 2001 From: Sachin Magar Date: Mon, 30 Jun 2025 11:00:01 +0530 Subject: [PATCH 1/6] updated doc for azure virtual network --- docs/integrations/microsoft-azure/azure-virtual-network.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/integrations/microsoft-azure/azure-virtual-network.md b/docs/integrations/microsoft-azure/azure-virtual-network.md index 2e2ccdc341..1b9df44a89 100644 --- a/docs/integrations/microsoft-azure/azure-virtual-network.md +++ b/docs/integrations/microsoft-azure/azure-virtual-network.md @@ -321,6 +321,13 @@ Use this dashboard to: Azure Virtual Network - Denied Traffic Flow +### Azure Virtual Network alerts +These alerts are metric based and will work for all Virtual Networks. + +| Alert Name | Description | Alert Condition | Recover Condition | +|:--|:--------------------------------------------------------------------------------|:----------------|:------------------| +| `Azure Virtual Network - Under DDoS attack` | This alert is triggered when maximum DDoS attack count is greater than 1.0785. | Count > 1.0785 | Count < = 1.0785 | + ## Upgrade/Downgrade the Azure Virtual Network app (optional) import AppUpdate from '../../reuse/apps/app-update.md'; From 21feee25dc7f244611accf84e66555387728b281 Mon Sep 17 00:00:00 2001 From: Sachin Magar Date: Mon, 30 Jun 2025 14:58:29 +0530 Subject: [PATCH 2/6] removed metric rule and metric collection setup for vnet app --- .../microsoft-azure/azure-virtual-network.md | 47 ++----------------- 1 file changed, 3 insertions(+), 44 deletions(-) diff --git a/docs/integrations/microsoft-azure/azure-virtual-network.md b/docs/integrations/microsoft-azure/azure-virtual-network.md index 1b9df44a89..db363b6064 100644 --- a/docs/integrations/microsoft-azure/azure-virtual-network.md +++ b/docs/integrations/microsoft-azure/azure-virtual-network.md @@ -95,19 +95,6 @@ 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 field in field schema -1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Logs > Fields**.
[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Logs** select **Fields**. You can also click the **Go To...** menu at the top of the screen and select **Fields**. -1. Search for the following fields: - - `tenant_name`. This field is tagged at the collector level and users 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). - - `location`. The region to which the resource name belongs. - - `subscription_id`. Id associated with a subscription where the resource is present. - - `resource_group`. The resource group name where the Azure resource is present. - - `provider_name`. Azure resource provider name (for example, Microsoft.Storage). - - `resource_type`. Azure resource type (for example, storageaccounts). - - `resource_name`. The name of the resource (for example, storage account name). - -3. Create the fields if it is not present. Refer to [create and manage fields](/docs/manage/fields/#manage-fields). - ### Configure Field Extraction Rules Create a Field Extraction Rule (FER) for Azure Virtual Network by following the instructions [here](/docs/manage/field-extractions/create-field-extraction-rule/). @@ -132,39 +119,11 @@ Create a Field Extraction Rule (FER) for Azure Virtual Network by following the | fields subscription_id, location, provider_name, resource_group, resource_type, resource_name ``` -### Configure metric rules - - * **Azure Observability Metadata Extraction Azure Virtual Network** - - In case this rule already exists, then no need to create it again. -```sql -Rule Name: AzureObservabilityMetadataExtractionAzureVirtualNetwork -``` - -```sql title="Metric match expression" -resourceId=/SUBSCRIPTIONS/*/RESOURCEGROUPS/*/PROVIDERS/MICROSOFT.NETWORK/VIRTUALNETWORKS/* tenant_name=* -``` -| Fields extracted | Metric rule | -|------------------|----------------| -| subscription_id | $resourceId._1 | -| resource_group | $resourceId._2 | -| provider_name | MICROSOFT.NETWORK | -| resource_type | VIRTUALNETWORKS | -| resource_name | $resourceId._3 | - ### Configure metrics collection -In this section, you will configure a pipeline for shipping metrics from Azure Monitor to an Event Hub, onto an Azure Function, and finally to an HTTP Source on a hosted collector in Sumo Logic. This step is required only for DDOS related metrics which comes after enabling DDOS protection in your virtual network. - -1. Create a hosted collector and tag `tenant_name` field.
Azure Storage Tag Tenant Name -2. [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. [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). -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 storage service (blob, queue, table, and file) and each storage account that you want to monitor. - * Choose `Stream to an event hub` as the destination. - * Select `AllMetrics`. - * 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 the ARM template. You can use the default policy `RootManageSharedAccessKey` as the policy name. -4. Tag the location field in the source with the right location value.
Azure Storage Tag Location -5. Enable the `DDOS protection` by following the instructions in Azure [documentation](https://learn.microsoft.com/en-us/azure/ddos-protection/manage-ddos-protection#enable-for-an-existing-virtual-network) +import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; + +cxxx ### Configure logs collection From 6af304368ab40446bde0430dbe00b14a6508add6 Mon Sep 17 00:00:00 2001 From: Sachin Magar Date: Mon, 30 Jun 2025 15:34:28 +0530 Subject: [PATCH 3/6] updated with new v2 app installation process --- .../microsoft-azure/azure-virtual-network.md | 22 ++++++++++++++----- 1 file changed, 17 insertions(+), 5 deletions(-) diff --git a/docs/integrations/microsoft-azure/azure-virtual-network.md b/docs/integrations/microsoft-azure/azure-virtual-network.md index db363b6064..637f72bd55 100644 --- a/docs/integrations/microsoft-azure/azure-virtual-network.md +++ b/docs/integrations/microsoft-azure/azure-virtual-network.md @@ -123,7 +123,7 @@ Create a Field Extraction Rule (FER) for Azure Virtual Network by following the import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; -cxxx + ### Configure logs collection @@ -200,15 +200,27 @@ In order to find virtual networks without any flow log resource, you can audit f Now that you have set up data collection, install the Azure Virtual Network Sumo Logic app to use the pre-configured [dashboards](#viewing-the-azure-virtual-network-app-dashboards) that provide visibility into your environment for real-time analysis of overall usage. -import AppInstallNoDataSourceV2 from '../../reuse/apps/app-install-index-apps-v2.md'; +import AppInstallIndexV2 from '../../reuse/apps/app-install-index-option.md'; - + + +As part of the app installation process, the following fields will be created by default: + +- `tenant_name`. This field is tagged at the collector level. 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). +- `location`. The region to which the resource name belongs to. +- `subscription_id`. ID associated with a subscription where the resource is present. +- `resource_group`. The resource group name where the Azure resource is present. +- `provider_name`. Azure resource provider name (for example, Microsoft.Network). +- `resource_type`. Azure resource type (for example, storage accounts). +- `resource_name`. The name of the resource (for example, storage account name). +- `service_type`. Type of the service that can be accessed with a Azure resource. +- `service_name`. Services that can be accessed with an Azure resource (for example, in Azure Container Instances the service is Subscriptions). ## Viewing the Azure Virtual Network app dashboards -import ViewDashboards from '../../reuse/apps/view-dashboards.md'; +import ViewDashboardsIndex from '../../reuse/apps/view-dashboards-index.md'; - + ### Overview From cef44a242bcd5f84f3fdfabe1b5135bda3f1f5e2 Mon Sep 17 00:00:00 2001 From: Sachin Magar Date: Mon, 30 Jun 2025 19:04:00 +0530 Subject: [PATCH 4/6] removed FER --- .../microsoft-azure/azure-virtual-network.md | 26 ++----------------- 1 file changed, 2 insertions(+), 24 deletions(-) diff --git a/docs/integrations/microsoft-azure/azure-virtual-network.md b/docs/integrations/microsoft-azure/azure-virtual-network.md index 637f72bd55..866c190447 100644 --- a/docs/integrations/microsoft-azure/azure-virtual-network.md +++ b/docs/integrations/microsoft-azure/azure-virtual-network.md @@ -95,30 +95,6 @@ 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 Field Extraction Rules - -Create a Field Extraction Rule (FER) for Azure Virtual Network by following the instructions [here](/docs/manage/field-extractions/create-field-extraction-rule/). - -* **Target Resource Extraction FER** - - ```sql - Rule Name: AzureVirtualNetworkTargetResourceIdExtractionFER - Applied at: Ingest Time - Scope (Specific Data): tenant_name=* FlowLogFlowEvent - ``` - - ```sql title="Parse Expression" - json field=_raw "target_resource_id", "category", "flow_log_resource_id" - | where category="FlowLogFlowEvent" - | toUpperCase(target_resource_id) as target_resource_id - | parse field=target_resource_id "/SUBSCRIPTIONS/*/RESOURCEGROUPS/*/PROVIDERS/*/*/*" as subscription_id, resource_group, provider_name, resource_type, resource_name - | parse field=resource_name "*/SUBNETS/*" as vnet_name, subnet_name nodrop - | parse field=flow_log_resource_id "NETWORKWATCHERS/NETWORKWATCHER_*/" as region_name nodrop - | if (!isBlank(region_name), toLowerCase(region_name), "global") as location - | if (resource_name matches /SUBNETS/, "SUBNETS", resource_type) as resource_type - | fields subscription_id, location, provider_name, resource_group, resource_type, resource_name - ``` - ### Configure metrics collection import MetricsSourceBeta from '../../reuse/metrics-source-beta.md'; @@ -216,6 +192,8 @@ As part of the app installation process, the following fields will be created by - `service_type`. Type of the service that can be accessed with a Azure resource. - `service_name`. Services that can be accessed with an Azure resource (for example, in Azure Container Instances the service is Subscriptions). +Also FER `AzureVirtualNetworkTargetResourceIdExtractionFER` will be created as part of the app installation process itself. + ## Viewing the Azure Virtual Network app dashboards import ViewDashboardsIndex from '../../reuse/apps/view-dashboards-index.md'; From 7618b630a5041112acc92afc2b95cfae0f4d4023 Mon Sep 17 00:00:00 2001 From: Amee Lepcha Date: Mon, 30 Jun 2025 20:11:41 +0530 Subject: [PATCH 5/6] Update docs/integrations/microsoft-azure/azure-virtual-network.md Co-authored-by: John Pipkin (Sumo Logic) --- docs/integrations/microsoft-azure/azure-virtual-network.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/microsoft-azure/azure-virtual-network.md b/docs/integrations/microsoft-azure/azure-virtual-network.md index 866c190447..569e46f98a 100644 --- a/docs/integrations/microsoft-azure/azure-virtual-network.md +++ b/docs/integrations/microsoft-azure/azure-virtual-network.md @@ -189,7 +189,7 @@ As part of the app installation process, the following fields will be created by - `provider_name`. Azure resource provider name (for example, Microsoft.Network). - `resource_type`. Azure resource type (for example, storage accounts). - `resource_name`. The name of the resource (for example, storage account name). -- `service_type`. Type of the service that can be accessed with a Azure resource. +- `service_type`. Type of the service that can be accessed with an Azure resource. - `service_name`. Services that can be accessed with an Azure resource (for example, in Azure Container Instances the service is Subscriptions). Also FER `AzureVirtualNetworkTargetResourceIdExtractionFER` will be created as part of the app installation process itself. From 98f3ecc47fd00604129aa327ea8bad54992bfdf0 Mon Sep 17 00:00:00 2001 From: Amee Lepcha Date: Mon, 30 Jun 2025 20:11:49 +0530 Subject: [PATCH 6/6] Update docs/integrations/microsoft-azure/azure-virtual-network.md Co-authored-by: John Pipkin (Sumo Logic) --- docs/integrations/microsoft-azure/azure-virtual-network.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/microsoft-azure/azure-virtual-network.md b/docs/integrations/microsoft-azure/azure-virtual-network.md index 569e46f98a..172bedc0dd 100644 --- a/docs/integrations/microsoft-azure/azure-virtual-network.md +++ b/docs/integrations/microsoft-azure/azure-virtual-network.md @@ -183,7 +183,7 @@ import AppInstallIndexV2 from '../../reuse/apps/app-install-index-option.md'; As part of the app installation process, the following fields will be created by default: - `tenant_name`. This field is tagged at the collector level. 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). -- `location`. The region to which the resource name belongs to. +- `location`. The region the resource name belongs to. - `subscription_id`. ID associated with a subscription where the resource is present. - `resource_group`. The resource group name where the Azure resource is present. - `provider_name`. Azure resource provider name (for example, Microsoft.Network).