Skip to content

OpenTelemetry Collector Pipeline Not Processing Spans Fix

DodaTech Updated 2026-06-24 2 min read

In this tutorial, you'll learn about OpenTelemetry Collector Pipeline Not Processing Spans Fix. We cover key concepts, practical examples, and best practices.

Your OpenTelemetry Collector receives spans but they never reach the backend — the logging exporter shows no output, the backend has zero data, but the collector reports spans received: 1000. The pipeline routing is missing or misconfigured.

The Problem

receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317

exporters:
  logging:
    loglevel: debug
  otlp:
    endpoint: jaeger:4317

# WRONG: no service.pipelines section

The collector receives data but discards it because no pipeline connects the receiver to an exporter.

Step-by-Step Fix

1. Define the pipeline service section

receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317

exporters:
  logging:
    loglevel: debug
  otlp:
    endpoint: jaeger:4317

service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [logging, otlp]

2. Add processors for data transformation

receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317

processors:
  batch:
    timeout: 1s
    send_batch_size: 512
  memory_limiter:
    check_interval: 1s
    limit_mib: 512

exporters:
  logging:
    loglevel: info
  otlp:
    endpoint: jaeger:4317

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [memory_limiter, batch]
      exporters: [logging, otlp]

3. Create separate pipelines for signals

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlp, logging]
    metrics:
      receivers: [otlp]
      processors: [batch]
      exporters: [prometheus]
    logs:
      receivers: [otlp]
      processors: [batch]
      exporters: [loki]

4. Verify pipeline health

# Check collector health endpoint
curl http://localhost:13133/health

# Check collector metrics
curl http://localhost:8888/metrics | grep otelcol_exporter

# Expected output
otelcol_exporter_sent_spans_total{exporter="logging"} 1000
otelcol_exporter_sent_spans_total{exporter="otlp"} 1000

5. Debug with logging exporter only

service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [logging]  # Temporarily remove other exporters

Expected output:

Span #0
    Trace ID: 1234abcd
    Span ID: 5678efgh
    Name: /api/users
    Start time: 2026-06-24 10:00:00.000
    End time: 2026-06-24 10:00:00.123

Prevention Tips

  • Always define service.pipelines sections for each signal type
  • Use the logging exporter for initial debugging
  • Add memory_limiter and batch processors for production
  • Monitor collector metrics for pipeline throughput
  • Verify pipeline routing matches expected signal types

Common Mistakes with collector pipeline

  1. Mixing let bindings with <- bindings in do notation, producing type errors
  2. Overlapping type class instances that cause GHC to reject the program with ambiguous dispatch errors
  3. Non-exhaustive pattern matches that compile with warnings then crash at runtime

These mistakes appear frequently in real-world OPENTELEMETRY code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

### What happens if a signal type has no pipeline?

The collector receives the data but drops it silently. For example, if your app sends traces but only a metrics pipeline is defined, traces are discarded. Define pipelines for each signal type your applications emit.

Can one receiver feed multiple pipelines?

Yes, a receiver can be listed in multiple pipelines. However, this duplicates the data processing. Use the routing processor or tail sampling processor to selectively forward data to different exporters instead.

How do I measure pipeline latency?

Use the batch processor's metrics: otelcol_processor_batch_batch_send_size and otelcol_processor_batch_timeout. Enable the telemetry section in the collector config to expose detailed pipeline metrics.

Built by the developers of DodaTech

Doda Browser, DodaZIP & Durga Antivirus Pro