Coralogix Helm Presets for Kubernetes

This reference covers the Coralogix abstractions built into the otel-integration Helm chart via presets. Do not use full service.pipelines overrides; use presets to enable features safely.

Core Presets

Infrastructure Explorer / Resource Catalog

For Infrastructure Explorer to populate, the following prerequisite chain must be complete:

1. kubernetesResources preset on the cluster-collector (enabled by default — do not disable it):

opentelemetry-cluster-collector:
  presets:
    kubernetesResources:
      enabled: true   # default; shown explicitly to prevent accidental disablement

2. Dedicated Exporter with Headers: The preset automatically wires the coralogix/resource_catalog exporter with the x-coralogix-ingress: metadata-as-otlp-logs/v1 header.

3. hostEntityEvents Preset on the agent for node-level Infra Explorer entries (enabled by default — do not disable it, except on GKE Autopilot where hostMetrics is unavailable):

opentelemetry-agent:
  presets:
    hostEntityEvents:
      enabled: true   # default; must be false on GKE Autopilot (requires hostMetrics)

Failure Mode: The resourcedetection/resource_catalog processor crashes on a daemonset with can't get K8s Instance Metadata; node name is empty. Do not enable kubernetesResources on the agent; it must run on the cluster-collector.

Multi-line Logs (Stack Traces)

The logsCollection preset uses a filelog receiver on /var/log/pods. Kubernetes writes logs in CRI format where every line — including individual stack trace lines — is tagged F (final). The standard partial/final recombine never triggers because it only groups P → F sequences.

To recombine multi-line entries (Java stack traces, Python tracebacks), use firstEntryRegex to detect the start of a new logical log entry:

opentelemetry-agent:
  presets:
    logsCollection:
      multiline:
        firstEntryRegex: '^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}'

See Coralogix multi-line log configuration.

Anti-Pattern: Wholesale Pipeline Overrides

Manual overrides of service.pipelines inside the otel-integration values file strip the default receivers and processors that populate Coralogix dashboards and Infra Explorer.

Symptom: Dashboards populate on one cluster but remain empty on another, despite identical chart versions. Resolution: Remove the custom service.pipelines block. Use presets.<feature>.enabled and extraProcessors / extraReceivers hooks. Wholesale overrides break the resource/metadata processor that sets cx.agent.type, silently breaking chart upgrades and correlation rules.