--- 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 # Microsoft Azure Event Hubs integration 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 integration configuration fields This documentation details the configuration fields required to set up the Microsoft Azure Event Hubs integration for Health Log Analytics within ServiceNow. This integration enables customers to stream log data from Azure Event Hubs into their ServiceNow instance for monitoring and analysis. Show full answer Show less ## Integration Setup Details * **Integration Name:** A unique, required name for the integration, which automatically updates the generic form name. * **Service Instance:** Required field specifying the ServiceNow service instance where log data is bound. * **Source:** Read-only field indicating the log data source, set to PubSub. * **Description:** Optional brief description to identify the integration. ## MID Server Configuration * **Execute on:** Choose between a specific MID Server or a MID Server cluster to process logs (required). * **Specific MID Server:** Select a MID Server with log ingestion enabled and basic authentication supported (mTLS not supported). If not enabled, Health Log Analytics will activate it automatically. Default max concurrent inputs per MID Server is 10, adjustable via MID Server properties. * **MID Server Cluster:** Supports only failover clusters for high availability. Log ingestion must be enabled on all cluster MID Servers. The system runs data input on one MID Server, failing over to others as needed. Clusters are validated for capacity if at least one MID Server has fewer than 10 inputs running. ## Event Hubs Data Retrieval Configuration * **Event Hubs Namespace:** Required scoping container for event hubs. * **Event Hub Name:** The specific event hub to fetch logs from (required). * **Consumer Group Name:** Required field specifying the consumer group to use; default is *$Default*. Customers can use existing or create new groups. * **Event Hub Credentials:** Required Azure Shared Access Signature (SAS) credentials. Customers can select existing or create new SAS credentials by providing the policy name and key. ## Advanced Settings * **Restore Point Rate:** Frequency of saving restore points based on the number of logs read. * **Processor Threads Count:** Number of threads used for processing log data. * **Sub Sample Drop Ratio:** Configures selective discarding of logs to reduce volume; default is -1 (no discard). * **Sub Sample Receive Ratio:** Controls selective receipt of logs to limit ingestion; default is -1 (all logs received). * **Operation Timeout (seconds):** Timeout for Event Hubs operations. * **Receive Idle Timeout (seconds):** Timeout for receive operations. * **Max Length in Bytes:** Maximum size of individual log messages; default is 32,766 bytes. * **Prefetch Count:** Number of logs to prefetch before processing. * **Max Batch Size:** Maximum events passed per processing call; default is 100. * **Default Timezone:** Time zone applied when log messages lack timezone info; default is GMT. * **Character Encoding:** Encoding for logs; default is UTF-8. * **Drop if Queue is Full:** Option to discard logs if MID Server load is high to maintain performance. ## Practical Application for ServiceNow Customers By accurately configuring these fields, ServiceNow customers can reliably ingest and process Azure Event Hubs log data into Health Log Analytics. This enables centralized log monitoring, fault tolerance with MID Server clusters, and fine-tuned control over data volume and processing through advanced parameters. Ensuring proper MID Server selection and credential management is critical for seamless integration and performance. Description of the fields on the Microsoft Azure Event Hubs integration configuration forms for Health Log Analytics. For the Microsoft Azure Event Hubs integration setup procedure, see [Set up a Microsoft Azure Event Hubs integration for Health Log Analytics](https://www.servicenow.com/docs/BnbAcmS7Srge6C5CjqBrJA "Set up an integration for streaming events from Microsoft Azure Event Hubs to your ServiceNow instance."). {#il-connector-hla-event-hubs-fields__table_t11_vvw_jfc__entry__2} | Field | Description | |-|-| | Integration Name | Unique name of this integration. For example: My Event Hubs integration. This field is required. Note: When you fill in this field, the generic name displayed on the form adjusts automatically to match the name you entered. | | Service Instance | The service instance (formerly the application service) to which to bind the log data. This field is required. | | Source | The source of the log data that the integration pulls to your ServiceNow instance: PubSub. This field is read-only. | | Description | Option to add a brief description of the integration to help identify it. | | Execute on | Option to select whether to use a specific MID Server or a MID Server cluster. This field is required. | | MID Server name | (Only when Execute on is set to Specific MID Server.) The MID Server to which the logs are streamed. Note: * You can only select a MID Server with log ingestion capability that supports basic authentication. MID Servers that support mTLS are not listed. * If log ingestion is not enabled on the selected MID Server, Health Log Analytics enables it automatically. * 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. {#il-connector-hla-event-hubs-fields__ul_zss_wtt_ngc} 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. {#il-connector-hla-event-hubs-fields__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). | [Table 1. Provide details] {#il-connector-hla-event-hubs-fields__table_t11_vvw_jfc} {#il-connector-hla-event-hubs-fields__table_dy2_g5t_ngc__entry__2} | | | |-|-| | 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. | | Consumer Group name | The Consumer Group to use. This field is required. Enter an existing Consumer group or create one in the event hub. The default value is $Default. | | Event Hub Credentials | The Event Hub credentials to use. This field is required. Select existing Azure Shared Access Signature (SAS) credentials or create the Azure SAS credentials to use. If you create new Azure SAS credentials, you must provide the SAS policy name and key. | [Table 2. Set data retrieval method] {#il-connector-hla-event-hubs-fields__table_dy2_g5t_ngc} {#il-connector-hla-event-hubs-fields__table_zgg_xvw_jfc__entry__2} | Field | Description | |-|-| | Restore point rate | The number of logs the integration can read before a restore point is saved. | | Processor threads count | The total number of processor threads. | | Sub sample drop ratio | The ratio of logs to discard. This setting determines the number of logs to group together, out of which one is dropped. It reduces the number of fetched logs. The default value is -1: no logs are discarded. For example, if you want one log out of every five to be dropped, change the value to 5. | | Sub sample receive ratio | The ratio of logs to receive. This setting determines the number of logs to group together, out of which one is received. It reduces the number of logs you receive. The default value is -1, meaning no logs are received. For example, if you want to receive one log out of every five, change the value to 5. | | Operation timeout (seconds) | The number of seconds to wait before timing out event hubs operations. | | Receive idle timeout (seconds) | The number of seconds to wait before timing out receive operations. | | Max length in bytes | The maximum length, in bytes, of log messages. The default value is 32766. | | Prefetch count | The number of logs received in advance of event hubs operations. | | Max batch size | The maximum number of events passed to a single process call. The default value is 100. | | Default timezone | The default time zone of logs. The system uses this default when the log does not specify a time zone. The default value is GMT. | | Character encoding | The character encoding for this integration. The default value is UTF-8. | | Drop if queue is full | Option to select discarding logs if there is a load on the MID Server. | [Table 3. Advanced settings] {#il-connector-hla-event-hubs-fields__table_zgg_xvw_jfc}