OTel Collector Integration

The OpenTelemetry (OTel) Collector is a vendor-neutral collection component that gathers metrics, logs, and traces using open standards and forwards them to Kloudfuse over OTLP. It is the right choice when you want open-standard instrumentation, native histogram support, or a collection pipeline that is not tied to a single vendor’s agent.

You run the Collector in your environment — as a Kubernetes DaemonSet, a Docker container, or a process on a standalone host — and add a Kloudfuse OTLP exporter to its pipeline.

The Collector’s source coverage is provided by receivers — pipeline components that ingest telemetry from a particular source, such as scraping a Prometheus endpoint, tailing container logs, reading host metrics, or accepting OTLP pushed from an instrumented application. To collect from a new source, you add the corresponding receiver to the Collector configuration and wire it into a pipeline; the telemetry it produces is exported to Kloudfuse alongside everything else the Collector gathers. The pages below document the receivers Kloudfuse users deploy most often and the pipeline configuration each one requires — see OTel Collector Receivers for the reference list.