Skip to main content

Configuring the Coralogix Destination

The Coralogix destination forwards logs, metrics, and traces to Coralogix for analysis and monitoring. This guide details configuration using the interface components:

Supported Data Types

📘 Logs | 📈 Metrics | 🚦 Traces

Configuration

FieldTypeDefaultRequiredDescription
NameStringnonetrueUnique identifier for the configuration.
API Private KeyStringnonetrueThe private key used to authenticate requests with Coralogix.
Application NameStringnonetrueCoralogix “Application Name” for categorizing logs and metrics.
DomainStringUS1 coralogix.ustrueThe Coralogix region or domain where data is sent. Supported Regions:
- US1: coralogix.us
- US2: cx498.coralogix.com
- AP1: coralogix.in
- AP2: coralogixsg.com
- AP3: ap3.coralogix.com
- EU1: coralogix.com
- EU2: eu2.coralogix.com
Subsystem NameStringnonefalseCoralogix “Subsystem Name” for further categorization.
Enabled Data TypesCheckboxMetrics, Logs, TracesThe telemetry data types you want to export.
Log Data FormatRadioCoralogixLog data format:
- Coralogix: Native format for full compatibility.
- OTLP: OpenTelemetry Protocol for standard interoperability.

Advanced Options

FieldTypeDefaultRequiredDescription
Flush Timeout (seconds)Int30falseWhen using Log Data Type (Coralogix), this is the seconds to wait per individual attempt to send data to a backend.
Timeout (seconds)Int5falseWhen using Log Data Type (OTLP), this is the maximum time to wait for a response from the backend per send attempt. If the backend doesn’t respond within this time, the request is considered failed.
Application Name AttributesListnonefalseOrdered list of resource attributes used for Coralogix Application Name.
Subsystem Name AttributesListnonefalseOrdered list of resource attributes used for Coralogix Subsystem.