Snippets

OpenTelemetry Collector config snippets

Complete collector configs for the jobs people configure most, each with the one mistake that usually breaks it. Every config is a whole file, not a fragment, and passes the collector's own validate command (otelcol-contrib v0.161.0) before it is published.

Sources

Tail a log file

Ship an application log file to your backend, and keep your place in it across collector restarts.

Logs

Get the config →

Receive syslog (RFC 5424 and RFC 3164)

Accept modern and legacy syslog on one collector, from network gear and hosts that speak nothing else.

Logs

Get the config →

Receive OTLP over gRPC and HTTP

The front door: accept OTLP from SDKs and other collectors, on both transports, for all three signals.

Logs · Metrics · Traces

Get the config →

Processors

memory_limiter and batch, in the right order

The two processors every pipeline needs, so a traffic spike neither kills the collector nor floods the backend.

Logs

Get the config →

Destinations

Prove data is flowing with the debug exporter

The first thing to reach for when nothing arrives: print what the collector actually receives.

Logs

Get the config →

Running more than one collector?

LinkMesh manages collector configuration across a fleet from one self-hosted control plane, with a built-in library of sources you activate instead of hand-editing YAML on every host.

Install LinkMesh →