Exporting traces to Jaeger

Copy Markdown View Source

See ImagePipe's request traces in a local Jaeger, sent through the OpenTelemetry SDK. This recipe assumes ImagePipe runs in your app. How the traces are built is explained in Request tracing. For image_pipe_server, set the tracing variables instead, and run Jaeger as below.

Run Jaeger

# docker-compose.yml
services:
  jaeger:
    image: cr.jaegertracing.io/jaegertracing/jaeger:2.19.0
    ports: ["16686:16686", "4317:4317", "4318:4318"]

Run docker compose up -d, then open http://localhost:16686. Jaeger accepts OTLP on ports 4317 (gRPC) and 4318 (HTTP).

Add the OpenTelemetry SDK

# mix.exs
# :opentelemetry_exporter before :opentelemetry, so the exporter starts
# before the SDK needs it
{:opentelemetry_exporter, "~> 1.8"},
{:opentelemetry, "~> 1.7"},

ImagePipe only depends on :opentelemetry_api, which :opentelemetry brings in.

Point the SDK at Jaeger

# config/config.exs
config :opentelemetry,
  span_processor: :batch,
  traces_exporter: :otlp,
  # the service name Jaeger shows
  resource: [service: %{name: "my_app"}]

config :opentelemetry_exporter,
  otlp_protocol: :http_protobuf,
  otlp_endpoint: "http://localhost:4318"
# config/test.exs
config :opentelemetry, traces_exporter: :none

For a release, move this configuration to config/runtime.exs and read the endpoint from an environment variable.

Attach the tracer

# lib/my_app/application.ex
ImagePipe.Telemetry.attach_tracer()

If your app doesn't trace its own requests and a proxy you control sets traceparent, add extract_inbound: true so ImagePipe's traces join the caller's (see inbound trace context).

Request an image. After the SDK's next batch export, Jaeger shows an image_pipe.request trace with child spans such as image_pipe.send, image_pipe.deliver, image_pipe.encode, image_pipe.transform.execute, and image_pipe.transform.operation. If your app already traces its requests, image_pipe.request appears inside your request's trace instead.

Troubleshooting missing traces

ImagePipe checks for the OpenTelemetry API when it compiles. If attach_tracer/1 raises that it needs the API, recompile ImagePipe:

mix deps.compile image_pipe --force

If no traces appear, check that traces_exporter isn't :none in the environment you run, and wait for the SDK's next batch export.