ipx-web and ipx-directory send no traces #213
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Only ipx sends traces to Tempo. ipx-web (Caddy) sends none and does not pass a traceparent on, so a page request's trace starts at ipx. ipx-directory sends none, and ipx does not put a traceparent on its requests to the directory, so a Directory page view is ipx's span alone. Wanted: Caddy's tracing directive to the same OTLP endpoint (one trace browser, Caddy, ipx, joining the page's own from #190); the directory with ipx's tracing-opentelemetry setup (service ipx-directory), reading traceparent, and ipx injecting it on directory calls; then the dashboard's traces row and the prod-check skill to cover all three.
Done and deployed: ipx-web in
a370876, the directory and ipx's propagation in44e75df. ipx-web: Caddy's tracing directive, on with WEB_TRACING=on (production only, so the tests and the sample do not log failed exports). The directory: a span a request, a child of the caller's traceparent, and a trace a refresher round with a span a feed; the exporter and traceparent parsing are shared in ipx_directory::otel. ipx sends traceparent on its directory calls and wraps each share in a span. Checked: GET /api/directory/{id} through Caddy with a known traceparent is one trace, ipx-web 125ms > ipx 124ms > ipx-directory GET /v1/feeds/{id} 39ms. Dashboard's Traces row (recent, slow, failed) and the prod-check skill cover all three. CLAUDE.md now says traces first.