...
In the Storage Account, click Access control (IAM) in the left menu, click + Add, and click Add Role Assignment.
Search for either the Storage Blob Data Contributor or Storage Blob Data Owner ??Storage Blob Data Reader?? role and select it and then click Next.
Click + Select members and search for the event hub application, select it, click Next.
Click Review + Assign.
Connection string
Users can either obtain a connection string or use Role Assignments to allow the collector to access the Event Hub.
In your Azure account, search for the Event Hubs service and click on it.
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
To capture Blob or Data Lake, see How Event Hubs Capture is charged to select a tier. Otherwise, select the cheapest tier and one throughput unit. If you need more resources, they can be added later.
Select “Review+Create,” then “Create.”
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 Event Hub
Add a name.
One partition count is usually enough.
Select the maximum retention time.
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.
The
$Defaultconsumer group is fine. Devo recommends that the event hub only be accessed by Devo. If any other entity is accessing the event hub, then each entity must have its own consumer group and Microsoft must be paid more.
Now, in the Event Hub Namespace, click onShared access policies, search the default policy namedRootManageSharedAccessKeyand click it.
Copy and write down the primary (or secondary) connection string to be used later in the configuration file.
Role assignment
Alternatively, users can grant the necessary permissions to the registered application to access the Event Hub without using the RootManageSharedAccessKey. Roles can be assigned in a variety of ways (e.g. inherited from the subscription group), but the following steps will show how to assign the necessary roles directly to the Event Hub Namespace.
...
In the Event Hub Namespace, click Access control (IAM) in the left menu, click + Add, and click Add Access Role Assignment.
...
Search for either the Azure Event Hubs Data Receiver or Azure Event Hubs Data Owner role and select it and then click Next.
...
Click + Select members and search for the previously created App registration, select it, click Next.
...
Click Review + Assign.
Create a shared access policy for sending data to the event hub.
...
Now, search for the Monitor service and click on it.
...
Click the Diagnostic Settings option in the left area.
A list of the deployed resources will be shown. Search for the resources that you want to monitor, select them, and click Select a resource and Add diagnostic setting.
...
Type a name for the rule and check the required category details (logs will be sent to the cloud.azure.eh.events table, and metrics will be sent to the cloud.azure.eh.metrics table).
...
Check Stream to an Event Hub, and select the corresponding Event hub namespace, Event hub name, and Event hub policy name.
...
...
Add diagnostic setting
Name the diagnostic setting.
Enable metrics and logs. The options will vary.
Enable “Stream to an event hub.”
Select the namespace, hub, and policy you created.
Click Save to finish the process.
...
Run It
In the Cloud Collector App, create an Azure Collector instance using this parameters template, replacing the values enclosed in < >.
...