Azure Events Hub 

The Azure Events Hub connector will crawl events published in the Azure Event Hub Server within a given timeframe (configuration-dependent). Execution will result in populating the following fields:

The Azure Events Hub connector performs full and incremental scans over an Azure Event Hub Server and will extract metadata and content from each object scanned. Each scanned object will be tagged with one of three possible actions: add, update, or delete, and can be routed to any Aspire pipeline as desired.

The connector, once started, can be stopped, paused or resumed via the Scheduler Component. Typically the start job will contain all information required by the job to perform the scan. When pausing or stopping, the connector will wait until all the jobs it published have completed before updating the statistics and status of the connector.

Azure Events Hub Connector

AppBundle Name

Azure Event Hub Connector

Factory Name

com.accenture.aspire:aspire-azureEH-source

Aspire Version

4.0

Inputs

AspireObject from a content source submitter holding all the information required for a crawl

Outputs

An AspireObject containing the event, content and metadata processed for each file

Configuration

This section lists all configuration parameters available to install the Azure Blob Application Bundle and to execute crawls using the connector.

Property

Type

Default

Description

namespacestring

Namespace for the Event Hub that we want to crawl, used for credentials.

eventHubName

string

Event Hub Name that we want to crawl, used for credentials.

sasKeyName

string

Name of the SAS Key token, used for credentials.

sasKeystring


Value of the SAS Key, used for credentials.

filterOptionsradio selectorTIME_RANGE

Indicates the type of timeframe to be used for the crawl, possible values:

  • From (TIME_RANGE)
  • All Time (ALL_TIME)
  • From - To (FROM_TO)
timeRangeOptionint6

Used when the TIME_RANGE option is selected, it contains a set amount of hours used to define the start of the timeframe for the crawl. Possible values:

  • Last hour: 1
  • Last 6 hours: 6
  • Last 12 hours: 12
  • Last day: 24
  • Last 2 days: 48
  • Last 3 days: 72
  • Last 4 days: 96
  • Last 5 days: 120
  • Last 6 days: 144
  • Last 7 days: 168

 

readUp

int0

Used when the ALL_TIME option is selected, it indicates if we consume events to the last message received at the moment to start the crawl or when the crawl does not receive events. Possible values:

  • Until to last message received: 0
  • No events received: 1

fromStartDate

datetime

Used when the FROM_TO option is selected, it contains the start datetime for the crawl's timeframe

 fromEndDatedatetime   Used when the FROM_TO option is selected, it contains the end datetime for the crawl's timeframe






  • No labels