Arize Phoenix

Open the official Arize Phoenix site and review the getting-started documentation before connecting production data. Create an account or workspace if required. For API products, generate a credential from the provider dashboard and store it in a server-side environment variable or secrets manager; do not expose secret keys in browser code. Start with the smallest official example request.

Test the specific capability you intend to use: OpenTelemetry tracing, evaluations, prompt analysis, retrieval diagnostics, experiments and debugging for LLM and agent systems. Use a small set of realistic inputs so you can compare results consistently. If several models, tiers or modes are available, run the same examples through each relevant option and record the differences in output quality, response time and consumption.

After the basic workflow works, integrate Arize Phoenix into the application or team process. Add timeouts, retries and error handling for network calls, keep provider request IDs in logs when available, and validate generated output before using it in consequential downstream actions. For creative tools, save the prompts and generation settings that produce repeatable results.

Before scaling, review the usage dashboard and current documentation. Set spending or rate controls where the service offers them, monitor failures and latency, and re-check pricing and limits before large production jobs.