https://arize-ai.slack.com/archives/C017QTPKE0H/p1714421148476719

Here is instrumenting code: endpoint = phoenix_collector_endpoint + "/v1/traces" resource = Resource(attributes={}) tracer_provider = trace_sdk.TracerProvider(resource=resource) span_otlp_exporter = OTLPSpanExporter(endpoint=endpoint) tracer_provider.add_span_processor(SimpleSpanProcessor(span_exporter=span_otlp_exporter)) trace_api.set_tracer_provider(tracer_provider=tracer_provider) DSPyInstrumentor().instrument()

Hey Dhar R. you are using a version of Phoenix that doesn't support OTEL. Is it possible for you to upgrade your phoenix? https://github.com/Arize-ai/phoenix/blob/main/MIGRATION.md#v2x-to-v300

ok

Cool, let us know if that works!

image like this? image: arizephoenix/phoenix:version-3.0.0

I would probably go all the way 😉 https://hub.docker.com/layers/arizephoenix/phoenix/version-3.24.0/images/sha256-499d[…]68e0921b31282a5eac5294adb892af9f1b318018f56bae07?context=repo

Here's a DSPy example https://github.com/Arize-ai/openinference/tree/main/python/examples/dspy-rag-fastapi

2024-04-29 15:18:38 ERROR:opentelemetry.exporter.otlp.proto.http.trace_exporter:Failed to export batch code: 405, reason: Method Not Allowed

also this now (used to work)

The screenshot might be a caching issue that we should have fixed. Can you clear your application data in the browser for me?

Trying to figure out why you get a 405...

no error details now but same screenshot as before

Hmm, that's really weird. The`TracingHomePageQuery` is def. a caching issue since that has been re-named. I'm afraid I can't 100% track down the issue from the code provided above. Any server logs as to why you might be getting a 405? I don't see what PHOENIX_COLLECTOR_ENDPOINT is set to. Is it set to something like

COLLECTOR_ENDPOINT=http://phoenix:6006/v1/traces

I'm guessing you are running docker compose Can you try something like this? https://github.com/Arize-ai/openinference/blob/main/python/examples/dspy-rag-fastapi/compose.yml#L13

yes. that is what I have

hey, the server is running now! had another tab open which is why it did not fully clear cache