rays
1724346da7
ipx had no spans, only log lines, so there was no way to see where a
slow scan, download or request spent its time. With
OTEL_EXPORTER_OTLP_ENDPOINT set, the daemon now exports traces over
OTLP/HTTP (Tempo on Tower): a scan, each feed in it, the feed fetch and
site icon lookup, downloads, torrents, reaps, and web requests. Log lines
inside a span ride along as its events.
Only the daemon exports: the healthcheck runs ipx status every 30s and
would bury everything else. The web event stream and the log view's
polling get no span, for the same reason. The exporter shares ipx's
reqwest 0.13, so no second HTTP stack comes in.
The stderr log now prefixes lines inside a span with it, as
tracing-subscriber's fmt layer does (scan{only=None force=false}: ...).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
30 lines
982 B
YAML
30 lines
982 B
YAML
services:
|
|
ipx:
|
|
image: 192.168.1.130:5000/ipx:latest
|
|
container_name: iPX
|
|
restart: unless-stopped
|
|
environment:
|
|
PUID: "99"
|
|
PGID: "100"
|
|
TZ: "America/Toronto"
|
|
IPX_LOG: "ipx=info"
|
|
# Traces to Tempo, in the monitoring project; ipx sends none without it.
|
|
OTEL_EXPORTER_OTLP_ENDPOINT: "http://192.168.1.130:4318"
|
|
# IPX_DATABASE_URL=postgres://... to use Postgres; without it, /data/state.db (SQLite).
|
|
env_file:
|
|
- ipx.env # relative: Arcane resolves it inside its own container
|
|
ports:
|
|
- "8099:8099" # web UI
|
|
- "6881:6881/tcp" # BitTorrent peers
|
|
- "6881:6881/udp" # DHT
|
|
volumes:
|
|
- /mnt/fast/appdata/ipx:/config # config.toml, and the web token
|
|
- /mnt/user/ipx/:/data # state.db
|
|
- /mnt/user/ipx/downloads:/downloads
|
|
healthcheck:
|
|
test: ["CMD", "ipx", "status"]
|
|
interval: 30s
|
|
timeout: 5s
|
|
retries: 3
|
|
start_period: 10s
|