---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Microsoft Azure Event Hubs data input configuration fields

# Microsoft Azure Event Hubs data input configuration fields {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Microsoft Azure Event Hubs data input configuration fields

This guide details the configuration fields for setting up Microsoft Azure Event Hubs as a data input source in ServiceNow, specifically for streaming log data into your instance.
It covers required fields for basic setup, options for using MID Servers or MID Server clusters to pull data, query settings, transport parameters, and advanced configuration options.
These configurations enable seamless integration and reliable log ingestion critical for monitoring and analytics.
Show full answer Show less  

## Basic Configuration

* **Name and Description:** Assign a unique name and an optional description to identify the data input.
* **Execute on:** Choose whether to use a specific MID Server or a MID Server cluster for data ingestion. This choice impacts failover and load distribution.
* **MID Server Selection:** When selecting a specific MID Server, only those supporting basic authentication are listed; mTLS-enabled servers are excluded. A single MID Server can handle up to 10 streaming data inputs by default, adjustable in MID Server properties.
* **MID Server Cluster:** For clusters, failover protection is provided by grouping multiple MID Servers. Data input runs on one MID Server and fails over to another if needed. Each MID Server in the cluster must have log ingestion enabled; this is automatically managed by Health Log Analytics where necessary.
* **Service Instance:** Bind the data input to an existing or newly created service instance (status set to Operational) to organize the log data properly.

## Read-Only Status Information

* Status of the data input (active or disabled)
* Transport protocol (utilizing Microsoft Azure Event Hubs)
* Count of log sources created by this input
* Timestamp when input was disabled or last logged
* Error messages related to streaming failures

## Query Settings

* **From:** Defines the starting date/time for reading event data; necessary to limit data volume and prevent congestion. Example: "Now -1 week".
* **Max batch size:** Limits the number of events processed per call to optimize performance (default example: 100).

## Transport Configuration

* **Event Hubs Namespace:** Required container name for the event hub(s).
* **Event Hub Name:** Specifies which event hub to fetch logs from.
* **Event Hub Credentials:** Shared access authorization policy required for authentication.
* **Consumer Group Name:** Selects the consumer group within the event hub to read from.

## Advanced Configuration

* **Restore Point Rate:** Number of events read before saving a restore point (default 100).
* **Processor Threads Count:** Number of threads used for processing events (default 2).
* **Operation Timeout:** Time in seconds to wait before timing out event hub operations (default 120).
* **Receive Idle Timeout:** Wait time in seconds before receive operations time out (default 60).
* **Prefetch Count:** Number of events to prefetch to improve performance (default 500).
* **Default Timezone:** Applied if log data lacks timezone information (default GMT).
* **Sub Sample Drop/Receive Ratios:** Settings to reduce the volume of fetched events by dropping or discarding events in batches (defaults -1, meaning disabled).
* **Max Length in Bytes:** Maximum event size allowed (default 32766 bytes).
* **Character Encoding:** Encoding format for the data input (default UTF-8).
* **Sleep Interval:** Time to wait before querying again after no events are found (default 60 seconds).
* **Polling Interval:** Interval for polling new events (default 0 seconds).
* **Drop if Queue is Full:** Option to discard logs when MID Server is under load (default false).

## Practical Benefits

This configuration enables ServiceNow customers to reliably ingest and process streaming logs from Microsoft Azure Event Hubs with failover support through MID Server clusters, customizable performance tuning, and robust error handling. Proper setup ensures efficient data flow, minimizes processing delays, and maintains operational visibility essential for IT service management and security analytics.  
Description of the fields on the Microsoft Azure Event Hubs data input
configuration form.

## Basic configuration {#hla-data-input-event-hubs-ref__section_evd_kv4_pvb}

{#hla-data-input-event-hubs-ref__table_bst_nhc_x4b__entry__2}

| Field | Description |
|-|-|
| Name | Name of the new data input. This field is required. |
| Description | Description of the data input. |
| Execute on | Option 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. {#hla-data-input-event-hubs-ref__ul_wjs_nz3_nsb}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. * 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. {#hla-data-input-event-hubs-ref__ul_htt_wdq_dwb} For more information about MID Server clusters, see [Configure a MID Server cluster](https://www.servicenow.com/docs/access?context=t_ConfigureAMIDServerCluster&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US). |
| Service instance | The service instance to which to bind the log data. Note: If no relevant service instance exists, [Create an service instance](https://www.servicenow.com/docs/access?context=create-it-services&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US) and add CIs to it. Set the status of the new service instance to Operational. This field is required. |
[ ]

{#hla-data-input-event-hubs-ref__table_bst_nhc_x4b}  
The following fields show read-only information: {#hla-data-input-event-hubs-ref__table_vcl_5s1_z4b__entry__2}

| Field | Description |
|-|-|
| Status | Status of the data input. |
| Transport | Protocol used to stream the log data. 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. |
| Disabled since | The time when the data input stopped or failed. |
| Last log 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. |
[ ]

{#hla-data-input-event-hubs-ref__table_vcl_5s1_z4b}  
{#hla-data-input-event-hubs-ref__table_qsq_sv4_pvb__entry__3}

| Field | Description | Example |
|-|-|-|
| 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 size | The maximum number of events passed to a single process call. | 100 |
[Table 1. Query settings tab]

{#hla-data-input-event-hubs-ref__table_qsq_sv4_pvb}  
{#hla-data-input-event-hubs-ref__table_wjh_g51_z4b__entry__2}

| 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. |
[Table 2. Transport tab]

{#hla-data-input-event-hubs-ref__table_wjh_g51_z4b}

## Advanced configuration {#hla-data-input-event-hubs-ref__section_eh4_kv4_pvb}

{#hla-data-input-event-hubs-ref__table_smn_fy3_x4b__entry__3}

| 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 timezone if the log doesn't include timezone 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. | UTF-8 |
| Sleep interval | The interval, in seconds, to wait before querying again after a query has returned no events. | 60 |
| Polling interval | The interval, in seconds, to wait before polling for new events. | 0 |
| Drop if queue is full | Option to discard logs if there is a load on the MID Server. | False |
[Table 3. Advanced configuration form]

{#hla-data-input-event-hubs-ref__table_smn_fy3_x4b}