Configure Applications to Send Telemetry

Before configuring your applications to export telemetry, we recommend starting with the Integration Overview. It explains how Coralogix uses the OpenTelemetry agent and collector to receive logs, metrics, and traces from your workloads.

Once the infrastructure components are in place, continue below to configure your instrumented applications to send telemetry to the local Coralogix agent running on the same Kubernetes node.

The Coralogix agent is deployed as a DaemonSet, so each Kubernetes node runs its own instance. For efficient node-local telemetry export, add the following environment variables to your application configuration:

- name: NODE_IP
  valueFrom:
    fieldRef:
      fieldPath: status.hostIP

- name: OTEL_EXPORTER_OTLP_ENDPOINT
  value: "$(NODE_IP):4317"

- name: OTEL_EXPORTER_OTLP_PROTOCOL
  value: "grpc"

- name: OTEL_EXPORTER_OTLP_INSECURE
  value: "true"

Explanation

• NODE_IP: Dynamically injects the IP address of the node where the pod is scheduled.
• OTEL_EXPORTER_OTLP_ENDPOINT: Targets the node-local Coralogix agent listening on port 4317.
• OTEL_EXPORTER_OTLP_PROTOCOL: Uses OTLP over gRPC, the recommended protocol for performance and interoperability.
• OTEL_EXPORTER_OTLP_INSECURE: Disables TLS encryption (suitable for trusted internal environments like Kubernetes).

Make sure all your telemetry-producing applications are configured this way when using Coralogix with Infrastructure Explorer.