Microsoft Azure Event Hubs data input configuration fields
reference brazil Updated Sep 10, 2026 4 min read hla-data-input-event-hubs-ref.md
Description of the fields on the Microsoft Azure Event Hubs data input configuration form.
|
Field |
Description |
|---|---|
|
Name |
Name of the new data input. This field is required. |
|
Description |
Optional description of the data input. |
|
Execute on |
Option to select whether to use a specific MID Server or a specific MID Server cluster. This field is required. |
|
MID |
(Only when the Execute on field is set to Specific MID Server) The MID Server to which log data from Microsoft Azure Event Hubs is pulled. This field is required.Note:
|
|
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:
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. This field is required.Selecting the service instance enables HLA to correlate CIs and service instances in the CMDB for root cause analysis. Note: If no appropriate service instance exists, create one, add CIs to it, and set its status to Operational. For more information, see Create a Service instance (application service). |
|
Field |
Description |
|---|---|
|
Status |
Status of the data input. This field is read-only. |
|
Transport |
Protocol used to stream the log data. This field is read-only.This data input uses Microsoft Azure Event Hubs to stream log data to your instance. |
|
Sources count |
The number of log sources this data input has created. This field is read-only. |
|
Disabled since |
The time when the data input stopped or failed. This field is read-only. |
|
MID last receiving time |
The time when the last log streamed in the data input. |
|
Error message |
The streaming error.This field is populated automatically. It displays only when a streaming error has occurred. |
|
Advanced |
Option to display the Advanced tab for advanced configuration. |
|
Field |
Description |
Example |
|---|---|---|
|
From |
Starting date and time for reading the data. Data older than this date and time is not read. This field is required.Note: Setting this value to a past date might require the system to read large amounts of data, causing congestion. |
Now -1 week |
|
Max batch size |
The maximum number of events passed to a single process call. |
100 |
| Field | Description | Default value |
|---|---|---|
| Restore Point Rate | The number of events the data input can read before a restore point is saved. | 100 |
| Processor Threads Count | The total number of processor threads. | 2 |
| Operation timeout | The number of seconds to wait before timing out event hubs operations. | 120 |
| Receive idle timeout | The number of seconds to wait before timing out receive operations. | 60 |
| Prefetch Count | The number of events received in advance of event hubs operations. | 500 |
| Default timezone | The default time zone used when the log doesn't include time zone information. | GMT |
| Sub sample drop ratio | The 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 ratio | The 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 bytes | The maximum length, in bytes, of events. | 32766 |
| Character encoding | The character encoding for this data input. This field is read-only. | UTF-8 |
| Polling interval | The interval, in seconds, to wait before polling for new events. | 0 |
| Drop if queue is full | Option to discard logs if many processes are waiting in the queue to access the MID Server. | Clear |
Parent Topic:Data input configuration fields
219 lines · 7.0 KB
--- title: Microsoft Azure Event Hubs data input configuration fields description: Description of the fields on the Microsoft Azure Event Hubs data input configuration form. locale: en-US canonical_url: https://www.servicenow.com/docs/r/it-operations-management/health-log-analytics/hla-data-input-event-hubs-ref.html release: brazil product: Health Log Analytics classification: health-log-analytics topic_type: reference last_updated: "2026-09-10" reading_time_minutes: 4 breadcrumb: [Data input configuration fields, Health Log Analytics reference, Health Log Analytics, ITOM AIOps, IT Operations Management] --- # Microsoft Azure Event Hubs data input configuration fields Description of the fields on the Microsoft Azure Event Hubs data input configuration form. <table id="table_bst_nhc_x4b"><thead><tr><th> Field </th><th> Description </th></tr></thead><tbody><tr><td> Name </td><td> Name of the new data input. This field is required. </td></tr><tr><td> Description </td><td> Optional description of the data input. </td></tr><tr><td> Execute on </td><td> Option to select whether to use a specific MID Server or a specific MID Server cluster. This field is required. </td></tr><tr><td> MID </td><td> \(Only when the **Execute on** field is set to Specific MID Server\) The MID Server to which log data from Microsoft Azure Event Hubs is pulled. This field is required.**Note:** - 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. </td></tr><tr><td> MID Server Cluster </td><td> \(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. - 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. This is true even when that MID Server is down. For more information about MID Server clusters, see [Configure a MID Server cluster](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/servicenow-platform/t_ConfigureAMIDServerCluster.md). </td></tr><tr><td> Service instance </td><td> The service instance to which to bind the log data. This field is required.Selecting the service instance enables HLA to correlate CIs and service instances in the CMDB for root cause analysis. **Note:** If no appropriate service instance exists, create one, add CIs to it, and set its status to Operational. For more information, see [Create a Service instance \(application service\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/servicenow-platform/create-it-services.md). </td></tr></tbody> </table><table id="table_vcl_5s1_z4b"><thead><tr><th> Field </th><th> Description </th></tr></thead><tbody><tr><td> Status </td><td> Status of the data input. This field is read-only. </td></tr><tr><td> Transport </td><td> Protocol used to stream the log data. This field is read-only.This data input uses Microsoft Azure Event Hubs to stream log data to your instance. </td></tr><tr><td> Sources count </td><td> The number of log sources this data input has created. This field is read-only. </td></tr><tr><td> Disabled since </td><td> The time when the data input stopped or failed. This field is read-only. </td></tr><tr><td> MID last receiving time </td><td> The time when the last log streamed in the data input. </td></tr><tr><td> Error message </td><td> The streaming error.This field is populated automatically. It displays only when a streaming error has occurred. </td></tr><tr><td> Advanced </td><td> Option to display the **Advanced** tab for advanced configuration. </td></tr></tbody> </table><table id="table_qsq_sv4_pvb"><thead><tr><th> Field </th><th> Description </th><th> Example </th></tr></thead><tbody><tr><td> From </td><td> Starting date and time for reading the data. Data older than this date and time is not read. This field is required.**Note:** Setting this value to a past date might require the system to read large amounts of data, causing congestion. </td><td> Now -1 week </td></tr><tr><td> Max batch size </td><td> The maximum number of events passed to a single process call. </td><td> 100 </td></tr></tbody> </table>|Field|Description| |-----|-----------| |Event Hubs namespace|The scoping container for the event hub or hubs. This field is required.| |Event Hub name|The event hub from which to fetch log data. This field is required.| |Event Hub Credentials|Shared access authorization policy with which to authenticate to the event hub. This field is required.| |Consumer group name|The Consumer Group to use. This field is required.| |Field|Description|Default value| |-----|-----------|-------------| |Restore Point Rate|The number of events the data input can read before a restore point is saved.|100| |Processor Threads Count|The total number of processor threads.|2| |Operation timeout|The number of seconds to wait before timing out event hubs operations.|120| |Receive idle timeout|The number of seconds to wait before timing out receive operations.|60| |Prefetch Count|The number of events received in advance of event hubs operations.|500| |Default timezone|The default time zone used when the log doesn't include time zone information.|GMT| |Sub sample drop ratio|The 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 ratio|The 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 bytes|The maximum length, in bytes, of events.|32766| |Character encoding|The character encoding for this data input. This field is read-only.|UTF-8| |Polling interval|The interval, in seconds, to wait before polling for new events.|0| |Drop if queue is full|Option to discard logs if many processes are waiting in the queue to access the MID Server.|Clear| **Parent Topic:**[Data input configuration fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-operations-management/health-log-analytics/hla-data-input-config-fields.md)
| title | Microsoft Azure Event Hubs data input configuration fields |
| description | Description of the fields on the Microsoft Azure Event Hubs data input configuration form. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/it-operations-management/health-log-analytics/hla-data-input-event-hubs-ref.html |
| release | brazil |
| product | Health Log Analytics |
| classification | health-log-analytics |
| topic_type | reference |
| last_updated | 2026-09-10 |
| reading_time_minutes | 4 |
| breadcrumb | Data input configuration fieldsHealth Log Analytics referenceHealth Log AnalyticsITOM AIOpsIT Operations Management |