Content Comparison

...

1. In the Storage Account, click Access control (IAM) in the left menu, click + Add, and click Add Access Role Assignment.

   Image Added

2. Search for either the Storage Blob Data Contributor or Storage Blob Data Owner role and select it and then click Next.

3. Click + Select members and search for the previously created App registration, select it, click Next.

4. Click Review + Assign.

5. Connection string

   Users can either obtain a connection string or use Role Assignments to allow the collector to access the Event Hub.

   1. In your Azure account, search for the Event Hubs service and click on it. 

   

   2. Create an Event Hub resource per region (repeat the steps below for each region):

   • Click Add.

   

   • Fill the mandatory fields keeping in mind that the Event Hub must be in the same region as the resources that you are going to monitor (and only need one per region). The Throughput Units option refers to the ingress/egress limit in MB/s (each unit is 1 MB/s or 1000 events/second ingress, 2 MB/s, or 4096 events/second egress). You should adjust it according to the data volume (this can be modified later).

   

   • The previous steps create an EventHub namespace; now go to Event Hubs, search the created one and click on it.

   

   • Now click on the + Event Hub button and create a new resource. You only need to fill the Name and Partition Count fields (the Partition Count field will divide the data into different partitions to make it easier to read large volumes of data). Write down the EventHub name to be used later in the configuration file.

   

   • Once the Event Hub is created in the namespace, click it and select Consumer Group in the left menu. Note that a dedicated Consumer Group for Devo needs to be created if the existing consumer groups are already in use.

   

   • Here you will see the Event Hub consumer groups. This will be used by the collector (or other applications) for reading data from the Event Hub. Write down the Consumer group name that you will use later in the configuration file.

   

   • Now, in the Event Hub Namespace, click on Shared access policies, search the default policy named RootManageSharedAccessKey and click it.

   

   • Copy and write down the primary (or secondary) connection string to be used later in the configuration file.

...