Skip to content
Star3

Tracing backends

hashspan emits standard OpenTelemetry spans. Whatever your OpenTelemetry SDK exports to, the transaction spans go there too. There is nothing hashspan-specific to configure.

Any OTLP endpoint

Section titled “Any OTLP endpoint”

The OTLP exporters read the standard environment variables:

Terminal window
OTEL_EXPORTER_OTLP_ENDPOINT=https://your-collector:4318
OTEL_EXPORTER_OTLP_HEADERS="authorization=Bearer <token>"
OTEL_SERVICE_NAME=my-agent

Jaeger

Section titled “Jaeger”

Jaeger accepts OTLP on port 4318 (HTTP) and 4317 (gRPC):

Terminal window
docker run --rm -p 16686:16686 -p 4318:4318 jaegertracing/jaeger:2.21.0

Set OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318 and open localhost:16686.

Grafana Tempo, Langfuse, Honeycomb

Section titled “Grafana Tempo, Langfuse, Honeycomb”

All three accept OTLP. Step-by-step guides for each are an open good first issue (#35). Until then, use each backend’s OTLP endpoint and headers with the variables above.