---
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


---

# Cribl

# Cribl integration configuration fields {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Description of the fields on the Cribl integration configuration forms for Health Log Analytics.
For the Cribl integration setup procedure, see [Set up a Cribl integration for Health Log Analytics](https://www.servicenow.com/docs/TffxMbncPL3U_5dZ3LmwTg "Set up an integration to enable Health Log Analytics to process Cribl log messages streaming into your ServiceNow instance.").
{#il-connector-hla-cribl-fields__table_ogk_rh4_jfc__entry__2}

| Field | Description |
|-|-|
| Integration Name | Unique name of this integration. For example: My Cribl 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. |
| MID Server name | The MID Server to which the Cribl logs are streamed. This field is required. |
| Port | The port on the MID Server used for listening to logs. This field is required. Important: Enter a unique port that no other application on the MID Server uses. Ask your security team to confirm that traffic on that port is allowed. |
| Description | Option to add a brief description of the integration to help identify it. |
| Transport (for push integrations) | The protocol used for streaming log messages to your ServiceNow instance: TCP. This field is read-only. |
| Source (for pull integrations) | The source of the log data that the integration pulls to your ServiceNow instance: Cribl. This field is read-only. |
[Table 1. Provide details]

{#il-connector-hla-cribl-fields__table_ogk_rh4_jfc} {#il-connector-hla-cribl-fields__table_wk2_nn4_jfc__entry__2}

| Field | Description |
|-|-|
| Cribl URL | The URL of the Cribl instance. This field is required. HLA uses this URL to establish the connection with the Cribl instance and make the necessary API calls. For example: * On-Prem: https://my-cribl.company.com:9000 * Cloud: https://myorg-12345abcde.cribl.cloud * Sandbox: https://sandbox-xyz789.sandbox.cribl.io {#il-connector-hla-cribl-fields__ul_zjq_wds_pfc} |
| Authentication method | The authentication method used by the Cribl integration. This field is required. The Cribl integration supports: * Token-based authentication: Required for Cribl Cloud and also supported for self-hosted (On-Prem) Cribl instances. * Basic authentication: Preferred for self-hosted (On-Prem) Cribl instances. {#il-connector-hla-cribl-fields__ul_vq2_lpx_tfc}Both of these authentication methods use the default credential alias: Cribl_Credential_Alias. For information about setting up credentials for the authentication method used by the Cribl integration, see [Set up Cribl integration authentication credentials](https://www.servicenow.com/docs/rMpyL8jJSafzTPPdfu7hCQ "Configure credentials in Health Log Analytics for the authentication method used by the Cribl integration."). Important: Verify that only one active credential record of each credentials type exists under the credential alias. |
| Worker Group | The Cribl Worker Group from which to stream log data to the instance. This field is required. The drop-down list displays Worker Groups based on the provided Cribl cloud instance URL and authentication method. For example: * default * dev-workers * prod-workers * staging-workers {#il-connector-hla-cribl-fields__ul_wvz_dyf_qfc} |
| Cribl route | The Cribl route that directs log data to a specific destination. This field is auto-populated with a drop-down list of all available routes, each configured with a default destination. Select the desired route from the list. This field is required. For example: * default * demo-route {#il-connector-hla-cribl-fields__ul_bht_gyf_qfc} |
| Cribl destination | The Cribl destination to which the log data is directed. This field is auto-populated and read-only. When HLA populates this field, it provides a link to the destination on the Cribl server. For example: sn_hla_cribl_tcp_json_abcdef |
[Table 2. Set up connection]

{#il-connector-hla-cribl-fields__table_wk2_nn4_jfc}