You open the Azure Event Hub Consumer agent configuration dialog from a workflow configuration: you can right-click the agent icon and select Configuration..., or double-click the agent icon.
Azure Event Hub Consumer agent configuration
Setting | Description |
---|---|
Profile | Select the Azure profile that has been configured with the connection details for the Azure Event Hub. For more information about how to configure the profile, refer to 1. Azure Profile. |
Partition | Enter the partition name of the event hub to be used by the agent. This field is optional. |
Storage Directory | Enter the directory path of where the data are to be collected from the EC server that the Event Hub Consumer agent will be using. |
Consumer Group | Enter the name of the consumer group the agent will be retrieving from. |
Start at latest (from end) | Events are selected from the last offset from when the workflow was started. If you select this option, there is a risk that data can be lost after a restart. |
Start at earliest (from beginning) | Events are collected from the first offset. If you select this option, there is a risk that events will be processed multiple times after a restart. |
Advanced Tab
The Advanced tab contains additional settings for checkpointing the offset of events collection when the workflow is initiated. When a directory path is specified in the Storage Directory field, these settings shall override the settings for "Start at latest (from end)" and "Start at earliest (from beginning)" in in the General tabGeneral tab.
Azure Event Hub Consumer agent - Advanced tab
Setting | Description |
---|---|
Ignore out of sequence range | Select this checkbox to enable the following options to predefine where you would like the reading of offset to take place after a workflow restarts. |
Start at latest (from end) | Events are selected from the last offset from when the workflow was started. If you select this option, there is a risk that data can be lost after a restart. |
Start at earliest (from beginning) | Events are collected from the first offset. If you select this option, there is a risk that events will be processed multiple times after a restart. |