--- 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 --- # MID-less integrations # MID-less integrations for Health Log Analytics {#ariaid-title1} Release version: Australia Updated May 4, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 MID-less integrations for Health Log Analytics Health Log Analytics (HLA) supportsMID-less integrationsthat enable direct streaming of log data from third-party sources to your ServiceNow instance without requiring a MID Server. This approach simplifies deployment, reduces infrastructure overhead, and streamlines log ingestion, especially for cloud-native sources. Show full answer Show less ## Role of the MID Server and Benefits of MID-less Integration * The traditional MID Server acts as an intermediary, collecting and forwarding log data, but requires deployment, maintenance, and scaling for high log volumes. * MID-less integrations bypass the MID Server, sending log data over HTTPS directly to ServiceNow, reducing complexity and operational costs. ## How MID-less Integrations Work * **ITOM Gateway:** A lightweight, cloud-native component you deploy to receive and route incoming log data to ServiceNow. Deployment scales with expected log volume. * **JSON Web Token (JWT):** Provides secure, time-limited authentication for data streams, eliminating the need to store credentials like AWS keys on your instance. ## Supported MID-less Integrations * AWS Firehose * Microsoft Azure Event Hubs * OpenTelemetry (OTLP) protocol integrations including Cribl Stream, OpenTelemetry Collector, and Splunk OpenTelemetry Collector **Note:** OTLP is a standardized, vendor-neutral protocol for collecting and correlating logs from diverse sources, streamlining setup and transport. ## When to Use MID-less Integrations * To reduce infrastructure by eliminating the MID Server. * To simplify onboarding with guided setup via the Integrations Launchpad. * For streaming logs from cloud-native sources where a MID Server is unnecessary. * To avoid storing third-party credentials directly on ServiceNow. **Important considerations:** ITOM Gateway setup is mandatory for MID-less integrations. If your requirements include on-premises data collection, bidirectional communication, or unsupported integration types, traditional MID Server deployments may be better suited. ## Setup from an MCP Client MID-less integrations can be configured from an AI-enabled MCP Client without accessing the ServiceNow UI. This requires the ITOM MCP Server Console to be active and OAuth-authenticated MCP Client connectivity. Health Log Analytics (HLA) supports integrations that stream log data directly to your ServiceNow instance without a MID Server. Use these integrations to simplify your deployment and reduce infrastructure overhead. ## Role of the MID Server in Health Log Analytics {#hla-mid-less-integrations-concept__section-what-is-mid-server} A Management, Instrumentation, and Discovery (MID) Server is a Java application that runs on a server in your network. In a standard HLA deployment, the MID Server acts as a relay between your log data sources and your ServiceNow instance. It collects, filters, and forwards log data on behalf of the instance. While MID Servers provide flexibility and support a wide range of integrations, they introduce additional infrastructure to deploy, maintain, and monitor. Organizations with high log volumes may also have to scale MID Server capacity over time. ## How MID-less integrations work {#hla-mid-less-integrations-concept__section-mid-less-overview} MID-less integrations bypass the MID Server entirely. Log data streams from your third-party source directly to ServiceNow over HTTPS, where it is queued and processed by HLA. This architecture relies on two components: ITOM Gateway : A lightweight, cloud-native component that receives incoming log data and routes it to your ServiceNow instance. You deploy ITOM Gateway based on your expected log volume. For more information, including deployment options and prerequisites, see [MID-less log streaming via ITOM Gateway in Health Log Analytics](https://www.servicenow.com/docs/Dy3xpF7022XHtmW7IiCVIg "Health Log Analytics (HLA) can receive log data from external sources directly through the ITOM Gateway, without routing data through a MID Server. This architecture supports cloud-native log sources such as Amazon Data Firehose, Cribl, and OpenTelemetry, and is required for high-volume HLA deployments."). JSON Web Token (JWT) : A secure, time-limited token used to authenticate the data stream between your log source and the ServiceNow datacenter. JWT authentication removes the requirement to store credentials such as AWS keys directly on your ServiceNow instance. For more information, see [Configure a JWT provider and token](https://www.servicenow.com/docs/8ggBPj9hGXTx7a9H2mYJug "Configure a JSON Web Token (JWT) provider and token to authenticate log streaming integrations sending data to Health Log Analytics (HLA) via ITOM Gateway. This configuration is required before you can activate any ITOM Gateway integration in Integrations Launchpad."). ## Supported MID-less integrations {#hla-mid-less-integrations-concept__section-supported-integrations} The following integrations support MID-less log streaming to Health Log Analytics. * [AWS Firehose](https://www.servicenow.com/docs/HDeVwU9NgyiGAHHFl76QXw "Set up an integration to stream log data from Amazon Data Firehose directly to the ServiceNow datacenter, where it’s queued for Health Log Analytics processing. There’s no need to store AWS keys on your ServiceNow instance.") * [Microsoft Azure Event Hubs (MID-less)](https://www.servicenow.com/docs/EyXGi4RsqqUDJL3jgeNWeQ "Set up an integration for streaming events from Microsoft Azure Event Hubs to your ServiceNow instance without a MID Server.") MID-less integrations using the OpenTelemetry (OTLP) protocol: * [Cribl Stream](https://www.servicenow.com/docs/hHsuoouL2C5fsnUBvpJYXw "Set up a Cribl Stream integration to stream Cribl log data directly to your ServiceNow instance, without a MID Server.") * [OpenTelemetry Collector](https://www.servicenow.com/docs/d6lhYudvaAZfPAvMnj1yDg "Set up an OpenTelemetry Collector integration to stream log data directly to your ServiceNow instance using the OpenTelemetry (OTLP) protocol, without a MID Server.") * [Splunk OpenTelemetry Collector](https://www.servicenow.com/docs/pQst5J0Am6vVeAUpiciasA "Set up a Splunk OpenTelemetry Collector integration to stream Splunk log data directly to your ServiceNow instance using the OpenTelemetry (OTLP) protocol, without a MID Server.") Note: * OTLP uses a standardized, vendor-neutral protocol to send application and system logs to HLA. It enables logs to be easily collected, processed, and correlated regardless of their origin or destination. * The MID-less OpenTelemetry integrations all use the same transport model and share a common setup procedure in the Integrations Launchpad. {#hla-mid-less-integrations-concept__ul_mpc_xgj_hjc} ## When to use MID-less integrations {#hla-mid-less-integrations-concept__section-when-to-use} Consider MID-less integrations when your organization wants to: * Reduce infrastructure by eliminating the requirement to deploy and maintain a MID Server * Simplify onboarding with a guided setup in the Integrations Launchpad * Stream log data from cloud-native sources, such as Amazon Data Firehose or Microsoft Azure Event Hubs, where a MID Server intermediary adds unnecessary complexity * Avoid storing third-party credentials on the ServiceNow instance Before choosing a MID-less integration, review the following: * MID-less integrations require ITOM Gateway. You must set up and configure ITOM Gateway before activating any MID-less integration. For more information, see [MID-less log streaming via ITOM Gateway in Health Log Analytics](https://www.servicenow.com/docs/Dy3xpF7022XHtmW7IiCVIg "Health Log Analytics (HLA) can receive log data from external sources directly through the ITOM Gateway, without routing data through a MID Server. This architecture supports cloud-native log sources such as Amazon Data Firehose, Cribl, and OpenTelemetry, and is required for high-volume HLA deployments."). * If your deployment requires on-premises data collection, bidirectional communication, or integration types not yet supported in MID-less mode, a MID Server based integration may be more appropriate. {#hla-mid-less-integrations-concept__ul_lvm_zjc_hkc} ## MID-less integration setup from an MCP Client {#hla-mid-less-integrations-concept__section_sgm_rjc_hkc} Set up MID-less integrations for HLA from an AI-enabled MCP Client without opening the ServiceNow UI. This capability requires the ITOM MCP Server Console to be active on your instance. In addition, your MCP Client must be connected to the ITOM MCP Server Console with valid OAuth credentials. For more information, see [MID-less log ingestion for HLA from an MCP Client](https://www.servicenow.com/docs/ovPXqcn6dKEnBuNLBjxiQA "Set up MID-less log ingestion integrations for Health Log Analytics (HLA) directly from an AI-enabled MCP Client, without opening the ServiceNow UI.").