Azure Event Hub

Cyderes has the ability to pull logs from Azure Event Hub. Event Hub is a fully managed, real-time data ingestion service. Current limitations of this integration include one hub per data type and limited throughput capacity. To learn more about Event Hub scalability and how to manage it, review Scaling with Event Hubs. Click here to read more about Azure Event Hub.

Azure App Prerequisite

For this integration, an Azure App must be created. More information can be found about how to do that in the documentation here.

Creating an Event Hub

1. This Event Hub Guide explains how to create new Event Hubs via Azure portal. Azure has instructions online to create new Event Hubs via Azure portal. Note: An Azure Event Hub Namespace is a collection of Event Hubs.
2. IMPORTANT: A separate Event Hub must be created for each data type

Access Configuration

1. For authentication, Cyderes utilizes Azure Active Directory to access Event Hubs resources. The security principal given to Cyderes must be tied to the Event Hubs resources (one of: Resource Group, Event Hub Namespace, Event Hub) with both roles Azure Event Hubs Data Receiver and Azure Event Hubs Data Sender. Cyderes also requires the sender role in order to fetch metadata around the runtime of the hub. More information about this can be found in this article.
2. When creating access for Cyderes, a separate consumer group only for Cyderes should be created. For more information regarding the creation of consumer groups, see Event Consumers Overview and Azure Instructions.
3. Send the following information for each created hub to Cyderes when completed:

From Azure:

• Namespace
• Name
• Environment (If something other than Azure Public Cloud)
• Identity (Azure Active Directory App)
  • Application (client) ID
  • Directory (tenant) ID
  • Secret ID
  • Secret Value
• Consumer Group (specific for Cyderes, group id)
• List of Partition IDs