Add Event Hubs to favorites (if not already): All Services -> Search for Event Hubs, click Star.
Click on “Event Hubs” (in left-most menu), then on the “+ Add” button
Create a Resource Group if you do not already have an appropriate group, or, select an existing Resource Group.
Choose an event hub namespace name. (It can only contain letters, numbers, and hyphens).
Select the Location and Pricing tier you want to use, this will largely depend on your organization and it’s size/cost tolerance.
If desired, add Availability Zone features and Tags, click Review + Create.
Click on the Event Hub you just created once Azure is done with the creation process.
Click “Shared access policies” (in second-left-most menu).
Click “+ Add” to add a new policy.
Choose name, such as “ReadOnlyAccessKey”.
Check only the Listen check box.
Click Create button.
Click on the policy you just created. Make a note of the connection string primary key field for later use.
Configuring an Event Hub
Note that this step is not required for all types of logs. Some log sources automatically create their own event hub within the namespace you created above. Blumira recommends creating an Event Hub for sake of clarity.
In the Azure portal, click on “Event Hubs” (in left-most menu).
Click on the event hub namespace you want to use for Blumira logs.
Click “Event Hubs” (in the second-left-most menu).
Click “+ Event Hub” to add a new event hub.
Choose an event hub name like blumira-log-stream. (It can only contain letters, numbers, periods, hyphens, and underscores.)
Leave all other defaults, like Create.
Configure Azure to Send Logs to an Event Hub
Note: Azure Monitor creates its own event hub called “insights-operational-logs”. You must still create an event hub namespace, but can skip creating an event hub.