ipx-web's spans are all named ipx-web #286

Closed
opened 2026-10-18 13:03:52 -07:00 by rays · 1 comment
Owner

Every span Caddy sends to Tempo is named ipx-web (web/Caddyfile, tracing { span ipx-web }), so in Tempo's lists and the trace view each request looks the same and only its url.path attribute says what it was; ipx's own spans are named GET /api/entries. Found reading slow ipx-web spans during a prod check. Caddy 2.11 takes placeholders in the span name, so it can be the request's method and path.

Every span Caddy sends to Tempo is named `ipx-web` (web/Caddyfile, `tracing { span ipx-web }`), so in Tempo's lists and the trace view each request looks the same and only its `url.path` attribute says what it was; ipx's own spans are named `GET /api/entries`. Found reading slow ipx-web spans during a prod check. Caddy 2.11 takes placeholders in the span name, so it can be the request's method and path.
rays added the bug label 2026-10-18 13:03:52 -07:00
Author
Owner

Fixed in 187729a: Caddy names each span {http.request.method} {http.request.uri.path}, e.g. GET /icons/solid/code-compare.svg, seen in Tempo after deploying ipx-web. The prod check's span list falls back to url.path.

Fixed in 187729a: Caddy names each span `{http.request.method} {http.request.uri.path}`, e.g. `GET /icons/solid/code-compare.svg`, seen in Tempo after deploying ipx-web. The prod check's span list falls back to `url.path`.
rays closed this issue 2026-10-18 13:05:25 -07:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: rays/ipx#286