You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/send-data/collect-from-other-data-sources/azure-blob-storage/block-blob/full-vnet-integration.md
+47-39Lines changed: 47 additions & 39 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,12 @@
1
1
---
2
2
id: block-blob-full-vnet-integration
3
3
title: Collect Logs from Azure Blob Storage with full vnet integration
4
-
sidebar_label: Collect block blow with full vnet integration
4
+
sidebar_label: Collect block blob with full vnet integration
5
5
description: Configure a pipeline to ship logs from the Azure Blob Storage all throughout a vnet and then to an HTTP source on a hosted collector in Sumo Logic.
6
6
---
7
7
8
+
import useBaseUrl from '@docusaurus/useBaseUrl';
9
+
8
10
Current solution to bring the block blob data from storage account in Sumo Logic creates a pipeline which assumes that the storage account being monitored will have public access enabled. If you just want your storage account behind a firewall follow the instruction [here](https://help.sumologic.com/docs/send-data/collect-from-other-data-sources/azure-blob-storage/block-blob/collect-logs/#step-3-enabling-vnet-integration-optional). But if you want that all of the components which are created through the arm template in azure, to be behind azure vnet (this includes event hub, azure functions, storage account, servicebus) then follow the below instructions :
9
11
10
12
1. Download this template [https://github.com/SumoLogic/sumologic-azure-function/blob/azure\_premium\_template\_vnet\_integration/BlockBlobReader/src/blobreaderdeploywithPremiumPlan.json](https://github.com/SumoLogic/sumologic-azure-function/blob/azure_premium_template_vnet_integration/BlockBlobReader/src/blobreaderdeploywithPremiumPlan.json). It creates Service Bus also with Premium tier.
@@ -17,70 +19,76 @@ Screenshot of the Virtual Network, Only Storage Service Endpoint is required in
17
19
Screenshot of the NSG rules. Everything can be set to default
4. You can restrict its access of Storage account containing flow logs to selected networks by going to Storage Account \-\> Networking. Subnet of storage account same as subnet configured in SUMOBRTaskConsumer and SUMOBRDLQProcessor VNe integration step.
29
+
4. You can restrict its access of Storage account containing flow logs to selected networks by going to Storage Account -> Networking. Subnet of storage account same as subnet configured in SUMOBRTaskConsumer and SUMOBRDLQProcessor VNet integration step.
26
30
Below is the screenshot of the storage account where NSG flow logs are stored.
27
31
Even the ip addresses are not required to be whitelisted in the firewall (this we will fix in our docs).
6. In all the three azure functions you can restrict inbound traffic by going to Function App \-\> Networking \-\> Inbound traffic configuration \-\> Access restrictions allowing only subnet created in step 1\.
35
+
5. Storage account the one created by ARM template, you can restrict its access to selected networks by going to Storage Account -> Networking
6. In all the three azure functions you can restrict inbound traffic by going to Function App -> Networking -> Inbound traffic configuration -> Access restrictions allowing only subnet created in step 1.
7. To enable functions to access storage account created by arm template you need to do following steps
42
+
7. To enable functions to access storage account created by arm template you need to do following steps:
37
43
1. Select content storage in Configuration Routing and select Outbound internet traffic under Application routing in Azure Function Vnet integration for each function.
10. The service bus created by arm template is on standard tier \- which does not support vnet integration. Follow the below steps to create a new Service bus on premium tier (supports premium tier)
62
-
1. create new service bus namespace with premium plan \-
10. The service bus created by arm template is on standard tier - which does not support vnet integration. Follow the below steps to create a new Service bus on premium tier (supports premium tier):
70
+
1. Create new service bus namespace with premium plan:
71
+
1. same resource group as old service bus
64
72
2. same location
65
73
3. partition enabled
66
74
4. public access for starting (under networking tab)
67
-
2. Once servicebus namespace is created, go to entity \> queue and create a new queue by the name "**blobrangetaskqueue**", with the following parameters:
68
-
Max queue size: 40
69
-
message size 1024
70
-
max delivery count 3
71
-
time to live 14 days
72
-
Message lock duration 5 min
73
-
enable dead letter queue
74
-
3. Update connection string to the below format \- in all three azure functions (Producer, consumer and DLQ). From newly created service bus on the premium tier under Shared access policies. Where you can select the [RootManageSharedAccessKey](https://portal.azure.com/#) and copy the primary key from it as the value of shared\_access\_key\_value:
4. Go to newly created service bus \> networking. Change public network access from all networks to selected networks, and select the vnet and subnet previously created and used with other resources
75
+
2. Once servicebus namespace is created, go to entity > queue and create a new queue by the name "**blobrangetaskqueue**", with the following parameters:
76
+
-Max queue size: 40
77
+
- Message size: 1024
78
+
- Max delivery count: 3
79
+
- Time to live: 14 days
80
+
-Message lock duration: 5 min
81
+
- Enable dead letter queue
82
+
3. Update connection string to the below format - in all three azure functions (Producer, consumer and DLQ). From newly created service bus on the premium tier under Shared access policies. Where you can select the [RootManageSharedAccessKey](https://portal.azure.com/#) and copy the primary key from it as the value of shared_access_key_value:
4. Go to newly created service bus > networking. Change public network access from all networks to selected networks, and select the vnet and subnet previously created and used with other resources
77
85
78
86
79
87
11. Enable Service endpoints for below services in your Vnet.
80
88
81
89
<img src={useBaseUrl('/img/send-data/blockblob/block-blob-service-endpoint-enabling-vnet.png')} alt="Enabling service endpoints in VNet" style={{border: '1px solid gray'}} width="800" />
82
90
83
-
12. Go to Function App \-\> BlobTaskConsumer \-\> Invocations you should be able to see below logs
91
+
12. Go to Function App -> BlobTaskConsumer -> Invocations you should be able to see below logs
0 commit comments