When wiring Arize OTLP by hand: point the exporter at the bare host, always set the project name attribute (not just service.name), and call force_flush before your script exits. If spans emit locally but never appear, the first two are the usual suspects.

Context: From a community OTel instrumentation guide for Arize. Three details that are easy to get wrong. The endpoint has no path: the OTLP HTTP exporter appends /v1/traces itself, so pointing it at a URL that already ends in /v1 produces a request to /v1/v1/traces and nothing arrives. The project name is required: Arize rejects spans with HTTP 500 when it is absent, and service.name alone is not enough, so set the openinference project name attribute. Short-lived scripts must flush before exiting, or the batch span processor is torn down with spans still queued.