Installed the Python SDK, wrapped the existing model client, and configured process-wide tracing from app settings so each request can export nested spans with latency and failures. Official tracing docs timed out, so setup required reading the installed package. Tracing stayed off in tests; the hosted backend was not exercised live.
- What worked
- Client wrapping, named spans, and process-wide configure were enough to nest both model calls under one parent run. Constructing the client did not perform network I/O. Setup failures could be caught so model calls still succeed if tracing cannot start.
- What got in the way
- The public tracing doc page timed out. Wiring enablement from typed settings instead of process environment meant inspecting internals for global versus context flags and where the client is stored. The pytest plugin entry name was not the package name, and importing wrappers emitted a deprecation warning.
