OpenTelemetry Collector Config Generator
Start a Collector configuration quickly, with the processors that production setups normally need.
Use the tool
Why this tool exists
Choose OTLP over gRPC and/or HTTP, then where traces, metrics and logs go: OTLP to a backend, a Prometheus scrape endpoint, or the debug exporter. The output defines receivers, memory_limiter and batch processors (memory_limiter first, as recommended), the exporters you selected and one pipeline per signal.
The YAML was parsed to check its structure, but not run against a Collector. Component names and options change between Collector versions, so validate with otelcol validate.
No data is sent anywhere: the work happens in your browser, so you can use it offline once the page has loaded.
How to use it
- Choose receiver protocols and an exporter per signal.
- Enter the OTLP endpoint and Prometheus port.
- Save as config.yaml.
- Run otelcol validate --config config.yaml.
Frequently asked questions
Why is memory_limiter first?
So it can refuse data before other processors allocate memory.
Does it add TLS?
The OTLP exporter keeps TLS verification on; add certificates for private CAs.
Which Collector distribution?
The core debug exporter, OTLP and Prometheus exporters are used.
Is my data sent anywhere?
No. Everything is processed in your browser, and the page makes no network requests with your input.