Introduction

Azure Event Hub is a big data streaming platform as well as an event ingestion service. It delivers a large number of messages from any source to respond immediately to business challenges. For more information on Azure Events Hub, see Azure Events Hub on Microsoft.

Environment and Access Requirements

Repository Support

The Azure Events Hub connector supports crawling the following the repositories:

Environment Requirements

To access the Azure Events Hub connector, a connection must be established to a valid Azure Events Hub Service.

Microsoft Azure Events Hub is a service that is independent of Accenture Aspire technologies and licenses. You can see this link for information on how to Create an event hub using Azure portal.

User Account Requirements

To access the Azure Events Hub, the following fields must be supplied. 

• Namespace
• Event Hub Name
• SAS Key Name
• SAS Key

When creating the Event Hub, you obtain the Namespace and Event Hub name. For the other 2 fields required for authentication, the SAS Key Name and the SAS Key, you can see this article on how to obtain a connection string, and get the values from that connection string. The connection string template looks like this:

Endpoint=sb://<FQDN>/;SharedAccessKeyName=<KeyName>;SharedAccessKey=<KeyValue>

Framework and Connector Features

Framework Features

Connector Features

The Azure Events Hub connector has the following features:

• Performs incremental crawling (so that only new/updated events are indexed)
• Runs from any machine with access to the given Events Hub source

• Retrieves any type of event and its attributes. The information is taken from the hub based on their post time. Listed below are the possible retrieval options.

  • From a previous time until now. For example: last hour, last 6 hours, last day, last 7 days.

  • From a specific datetime, to another specific datetime
  • All events in the hub

Content Crawled

The Azure Events Hub connector can crawl the following objects: