Free Validation Tool

OTel Collector Config Checker

Validate your OpenTelemetry Collector configuration instantly. Catch errors, find deprecated fields, and get security recommendations.

OTel Collector Config (YAML)
Validation Results

Paste your config and click "Check Config" to validate

Example: Minimal Production-Ready Config
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317
      http:
        endpoint: 0.0.0.0:4318
        cors:
          allowed_origins:
            - "https://*.yourdomain.com"

processors:
  batch:
    timeout: 1s
    send_batch_size: 1024
  memory_limiter:
    check_interval: 1s
    limit_mib: 1000
    spike_limit_mib: 200
  resourcedetection:
    detectors: [env, system]
    timeout: 5s

exporters:
  otlphttp:
    endpoint: https://your-backend.com
    headers:
      Authorization: "Bearer ${API_KEY}"
    compression: gzip
    retry_on_failure:
      enabled: true
      initial_interval: 5s
      max_interval: 30s
      max_elapsed_time: 300s

extensions:
  health_check:
    endpoint: 0.0.0.0:13133
  zpages:
    endpoint: 0.0.0.0:55679

service:
  extensions: [health_check, zpages]
  pipelines:
    traces:
      receivers: [otlp]
      processors: [memory_limiter, batch]
      exporters: [otlphttp]
    metrics:
      receivers: [otlp]
      processors: [memory_limiter, batch]
      exporters: [otlphttp]
    logs:
      receivers: [otlp]
      processors: [memory_limiter, batch]
      exporters: [otlphttp]
  telemetry:
    logs:
      level: info
    metrics:
      address: 0.0.0.0:8888

What We Check

Validation Errors

YAML syntax errors, missing required fields, and invalid configurations.

Deprecated Fields

Outdated settings that may be removed in future versions.

Missing Components

Recommended processors and exporters for production use.

Security Settings

TLS configuration, authentication, and secure endpoint settings.