Page History
The Azure Events Hub Connector will crawl content from a Azure Events Hub repository.
| Easy Heading Free | ||||||
|---|---|---|---|---|---|---|
|
Introduction
The Azure Events Hub connector can scan and fetch the contents of an Azure Events Hub repository.
Environment and Access Requirements
Repository Support
The Azure Events Hub connector supports crawling the following the repositories:
| Repository | Version | Connector Version |
|---|---|---|
| Azure Events Hub | All | 5.1 |
Account Privileges
For the Azure the Azure Events Hub connector Hub connector to be able to crawl content, the Aspire Worker nodes must be run with an account with an account with that has the necessary permissions.
Environment Requirements
In order 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. For more information on Azure Events Hub see Azure Events Hub on Microsoft. You can also see this link for information on how to Create an event hub using Azure portal.
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
| Name | Supported |
|---|---|
| Content Crawling | Yes |
| Identity Crawling | Yes |
| Snapshot-based Incrementals | Yes |
| Non-snapshot-based Incrementals | No |
| Document Hierarchy | Yes |
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 events 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 is able to crawl the following objects:
| Name | Type | Relevant Metadata | Content Fetch and Extraction | Description |
|---|
Limitations
The Azure Events Hub Connector has the following limitations:
<Limitation 1>| Partition | container | N/A | ||
| Events | document | Yes |
Overview
Content Tools