Set up Cribl to send data to HLA without a MID serverRequirements Cribl Stream (cloud or self-hosted)Network permissions allow for for sending data to an API endpoint hosted on service-now.comActive log data in Cribl StreamAn active OpenTelemetery (MID-less) HLA data input on your instance (see KB2117238 - Configure a 3rd-party agent or OpenTelemetry Collector to send logs to HLA) Configuring Cribl Stream Cribl Stream supports many different destination types for log data, once you have an active OpenTelemetry (MID-less) data input, create a new Cribl Stream Destination for OpenTelemetry. We'll be configuring this to send data to HLA. Detailed documentation is available on the Cribl documentation site at https://docs.cribl.io/edge/4.1/destinations-otel/ (choose the appropriate version of Cribl Stream you are using for the most up-to-date instructions). HTTP or gRPC OpenTelemetry protocols are supported, however we recommend using gRPC as it is more efficient. Create a new OpenTelemetry Destination In Cribl Stream, create a new OpenTelemetry destination with the following values under "General Settings": OTLP version: 1.3.1Protocol: gRPC (preferred) or HTTP (if gRPC is not working)Endpoint (using the regional gateway subdomain from the data input configuration) INSERT_REGIONAL_GATEWAY_HERE.sncapps.service-now.com:443 (if using gRPC Protocol)https://INSERT_REGIONAL_GATEWAY_HERE.sncapps.service-now.com (if using HTTP Protocol) Logs path (HTTP only): /ingest/otlp/v1/logs Next, click "Authentication": in the "Token" field paste your access token from your data input. Finally, click "Advanced Settings", for gPRC (under "metadata") or HTTP (under "Additional Headers"), add the following key/values that will allow Cribl to authenticate with ServiceNow: Key: servicenow-integration-id, Value: Your integration ID from advanced settings in your HLA data inputKey: servicenow-access-token, Value: Your ServiceNow access token from advanced settins in your HLA data input Click "Save" and your Cribl destination is now ready to send data to HLA. As your send more data to HLA, return to Cribl Stream to adjust performance settings and check for errors. We recommend creating a single Cribl destination per HLA data input type: this makes it easier to manage HLA configuration and prevents different log types from being accidentally sent to the same data input. Troubleshooting If you see any errors, refer to KB1957226 for troubleshooting suggestions.