Set up authentication credentials for the Cribl integration in Health Log Analytics

  • Versão de lançamento: Australia
  • Atualizado 12 de mar. de 2026
  • 1 min. de leitura

    • Configure credentials for the authentication method used by the Cribl integration.

    Antes de Iniciar

    Decide on the appropriate authentication method for your instance:
    • Basic authentication is preferred for self-hosted (On-Prem) Cribl instances.
    • Token-based authentication is required for Cribl Cloud instances.
      Nota:
      Token-based authentication is also supported for self-hosted (On-Prem) Cribl instances.
    For token-based authentication, create a client ID and a client secret on your Cribl instance and use them to generate a token. For example:
    • Client ID: 1234567890abcdef
    • Client secret: abcdef1234567890

    For detailed information on the Cribl API, refer to the Cribl API documentation.

    Role required: evt_mgmt_admin

    Procedimento

    1. Navigate to All > Connections & Credentials > Connection & Credential Aliases.
    2. Select the default Cribl credential alias: Cribl_Credential_Alias.
    3. Select New to create a credential record.
    4. Select the appropriate credentials type for your Cribl instance:
      • For basic authentication, select Basic Auth Credentials.
      • For token-based authentication, select Custom Header API Key Credential.
    5. On the displayed form, fill in the fields.
      • For basic authentication:
        Tabela 1. Basic Auth credentials fields
        Field Description
        Name A name that describes the credentials.
        Username Your Cribl server username. For example: admin.
        Password Your Cribl server password. For example: admin123.
      • For token-based authentication:
        Tabela 2. Custom Header API Key credential fields
        Name A name that describes the credential.
        API Key The authentication token you generated on the Cribl instance.
    6. Select Save to save the credentials configuration.

    O que Fazer Depois

    • Verify that the provided credentials have appropriate permissions to access your Cribl instance.
    • Verify that only one active credential record of each credentials type exists under the credential alias.