Skip to content
Data input configuration fields › Health Log Analytics reference › Health Log Analytics › ITOM AIOps › IT Operations Management
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Microsoft Azure Event Hubs data input configuration fields

Description of the fields on the Microsoft Azure Event Hubs data input configuration form.

Basic configuration

FieldDescription
NameName of the new data input. This field is required.
DescriptionDescription of the data input.
Execute onOption to select whether to use a specific MID Server or a MID Server cluster. This field is required.
MID

(Only when the Execute on field is set to Specific MID Server)

MID Server to which log data from Microsoft Azure Event Hubs is pulled. Note:

  • You can select only MID Servers that support basic authentication. MID Servers that support mTLS are not listed.
  • The default maximum number of data inputs streaming logs to a single MID Server is 10. You can modify this number in the MID Server properties.
  • If log ingestion is not enabled for the selected MID Server, Health Log Analytics enables it automatically.

This field is required.

MID Server Cluster

(Only when Execute on is set to Specific MID Server cluster.)

The MID Server cluster to which the log data is pulled. This field is required.The data input runs on a single MID Server in the cluster until that MID Server fails. The system then moves all the data input tasks to the next available MID Server in the cluster according to the configured order.

Note:

  • Health Log Analytics supports only failover MID Server clusters. In these clusters, multiple MID Servers are grouped together for failover protection. When selecting a cluster from the data input or integration form, the MID Server clusters list displays only failover clusters.
  • The MID Server cluster must include only MID Servers that support basic authentication. mTLS is not supported for log ingestion.
  • Log ingestion must be enabled for each MID Server in the cluster. If log ingestion is not enabled for the active MID Server, Health Log Analytics enables it automatically.
  • The default maximum number of data inputs or integrations streaming logs to a single MID Server is 10. A cluster passes capacity validation if it contains at least one MID Server with fewer than 10 data inputs or integrations running on it, even when that MID Server is down.

For more information about MID Server clusters, see Configure a MID Server cluster.

Service instance

The service instance to which to bind the log data.Note: If no relevant service instance exists, Create an service instance and add CIs to it. Set the status of the new service instance to Operational.

This field is required.

The following fields show read-only information:

FieldDescription
StatusStatus of the data input.
TransportProtocol used to stream the log data.This data input uses Microsoft Azure Event Hubs to stream log data to your instance.
Sources countThe number of log sources this data input has created.
Disabled sinceThe time when the data input stopped or failed.
Last log timeThe time when the last log streamed in the data input.
Error messageThe streaming error.This field is populated automatically. It displays only when a streaming error has occurred.
FieldDescriptionExample
From

Starting date and time for reading the data. Data older than this date and time is not read.Note: Setting this value to a past date might require the system to read large amounts of data, causing congestion.

This field is required.

Now -1 week
Max batch sizeThe maximum number of events passed to a single process call.100
FieldDescription
Event Hubs namespaceThe scoping container for the event hub or hubs. This field is required.
Event Hub nameThe event hub from which to fetch log data. This field is required.
Event Hub credentialsShared access authorization policy with which to authenticate to the event hub. This field is required.
Consumer Group nameThe Consumer Group to use.This field is required.

Advanced configuration

FieldDescriptionDefault value
Restore point rateThe number of events the data input can read before a restore point is saved.100
Processor threads countThe total number of processor threads.2
Operation timeoutThe number of seconds to wait before timing out event hubs operations.120
Receive idle timeoutThe number of seconds to wait before timing out receive operations.60
Prefetch countThe number of events received in advance of event hubs operations.500
Default timezoneThe default timezone if the log doesn't include timezone information.GMT
Sub sample drop ratioThe number of events to batch together, out of which one will be discarded. This setting is used to reduce the number of fetched events.-1
Sub sample receive ratioThe number of events to batch together, out of which all but one will be discarded. This setting is used to decrease the number of received events.-1
Max length in bytesThe maximum length, in bytes, of events.32766
Character encodingThe character encoding for this data input.UTF-8
Sleep intervalThe interval, in seconds, to wait before querying again after a query has returned no events.60
Polling intervalThe interval, in seconds, to wait before polling for new events.0
Drop if queue is fullOption to discard logs if there is a load on the MID Server.False

Parent Topic:Data input configuration fields