Send OpenTelemetry traces to Tempo #87

Closed
opened 2026-09-29 06:17:59 -07:00 by rays · 1 comment
Owner

ipx only logs; there are no spans, so there is no way to see where a slow scan, request or download spends its time. Tempo is now running on Tower (OTLP on 192.168.1.130:4317/4318). ipx should send traces over OTLP when OTEL_EXPORTER_OTLP_ENDPOINT is set, with spans for web requests, feed scans and downloads.

ipx only logs; there are no spans, so there is no way to see where a slow scan, request or download spends its time. Tempo is now running on Tower (OTLP on 192.168.1.130:4317/4318). ipx should send traces over OTLP when OTEL_EXPORTER_OTLP_ENDPOINT is set, with spans for web requests, feed scans and downloads.
rays added the enhancement label 2026-09-29 06:17:59 -07:00
Author
Owner

Fixed in 1724346, 9e7c93e and 549ae33: the daemon sends traces over OTLP/HTTP when OTEL_EXPORTER_OTLP_ENDPOINT is set (scans, feeds, fetches, site icons, downloads, torrents, reaps, web requests named by route). Production sends to Tempo at 192.168.1.130:4318 tagged deployment.environment.name=production; the browser suite's daemon has the endpoint blanked. Deployed.

Fixed in 1724346, 9e7c93e and 549ae33: the daemon sends traces over OTLP/HTTP when OTEL_EXPORTER_OTLP_ENDPOINT is set (scans, feeds, fetches, site icons, downloads, torrents, reaps, web requests named by route). Production sends to Tempo at 192.168.1.130:4318 tagged deployment.environment.name=production; the browser suite's daemon has the endpoint blanked. Deployed.
rays closed this issue 2026-09-29 06:35:45 -07:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: rays/ipx#87