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

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Set up MID-less log ingestion

# Set up MID-less log ingestion using an MCP Client {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Create, configure, and activate MID-less log ingestion integrations for Health Log Analytics from an MCP Client.

## Before you begin

Verify that:

* The ITOM Gateway is set up and configured on your ServiceNow instance. For more information, see [MID-less log streaming via ITOM Gateway in Health Log Analytics](https://www.servicenow.com/docs/J7jjYG2Bko88VdNZdNHtbg "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.").
* The ITOM MCP Server Console is active on your instance.
* Your MCP Client application is connected to the ITOM MCP Server Console with valid OAuth credentials.
* The Health Log Analytics plugin is installed on your instance.
{#itom-mcp-server-hla-ingest-setup__ul_hla_ingest_prereqs}

For more information about setting up MID-less integrations from an MCP Client, see [MID-less log ingestion for HLA from an MCP Client](https://www.servicenow.com/docs/kLxwAEXjOy_F9jkGkVb4WQ "Set up MID-less log ingestion integrations for Health Log Analytics (HLA) directly from an AI-enabled MCP Client, without opening the ServiceNow UI.").

Role required: evt_mgmt_admin or sys_admin (for JWT provider and token configuration)

## Procedure

1. Open your MCP Client application.
2. In the MCP Client application, ask to create a MID-less integration.  
   Use natural language. For example: "Create an OTel integration named otel-prod."  
   If no integration with that name exists, the integration is created in a draft, inactive state. The following information is returned:  
   * Integration ID
   * HTTP endpoint
   * gRPC endpoint
   * Access token
   {#itom-mcp-server-hla-ingest-setup__ul_hla_ingest_created_fields}
3. Review the returned integration details.
4. Ask the MCP Client to activate the integration.
5. Request the setup information for your integration type.  
   The following table lists what to ask for, based on integration type.

   | Integration type | What to do |
   | OTel | Ask your MCP Client to generate an OTel collector `exporters` configuration block, then add it to your collector.yaml file. |
   | Other MID-less integration types | Ask your MCP Client to help you complete the setup information specific to that integration type outside ServiceNow. For example, for Amazon Data Firehose, ask it to help you set up a Firehose stream in your AWS account. |
   |-|-|

6. **Optional:** Ask the MCP Client to rename the integration.  
   Note:  
   The integration must be inactive to be renamed. The integration is automatically deactivated, renamed, and reactivated.

## Result

The integration is active and ready to receive log data at the returned endpoint. On the Integrations Launchpad, the integration tile is available in the Installed integrations tab.

## What to do next

Verify that log data is arriving in HLA.

To rotate credentials, ask the MCP Client to refresh the integration's token. The previous token remains valid until its original expiration.