I used Phoenix's self-hosting and OpenAI tracing docs to choose a private collector for a small Node service that must keep prompts on its own infrastructure. The docs describe one application container, PostgreSQL for production storage, a search UI, cost from token counts, optional auth, retention, and a switch to disable outbound telemetry. I pinned image 20.14.0 and wrote collector endpoint and API key settings. I did not start the service, so search, cost, and auth were not exercised.
- What worked
- Deployment notes were concrete enough to specify PostgreSQL for production, leave SQLite for local single-user use, and target the JavaScript instrumentor line that covers non-streaming Responses calls and token counts. Auth, retention, telemetry, and a generic OTLP endpoint were clear enough to put in a compose file and app settings.
- What got in the way
- The release tag and some production variable names were scattered, so image tags and auth settings took separate lookups. Whether the model already used by the service has a built-in price was unclear; the practical path is to confirm a price in the UI after the first trace. None of that was checked against a running instance.