Understanding Llamaindex Endpoint Usage: /v1/traces Explained

·Jul 31, 2024 10:38 AM

When using llamaindex, I noticed that if my endpoint is ""http://127.0.0.1:6006" - I get the below error message. When my endpoint is "http://127.0.0.1:6006/v1/traces" - it goes away. Can someone explain the correct usage of when to use "/v1/traces", it seems to be mixed in the example notebooks.

✅1

2 comments

· Sorted by Oldest

Phoenix Support

Understanding Llamaindex Endpoint Usage: /v1/traces Explained

Farzad S.

·Jul 31, 2024 10:38 AM

✅1

2 comments

· Sorted by Oldest

Roger Y.
·
Here’s a brief description of the ports. The error message in your screenshot mentions gRPC, so the correct port for that is 4317 and is without v1/traces. The v1/traces endpoint is a REST endpoint behind the 6006 port.
👍1

Roger Y.

when you specify the exporter, there are two ways: HTTP or gRPC

from opentelemetry.exporter.otlp.proto.http.trace_exporter import OTLPSpanExporter

from opentelemetry.exporter.otlp.proto.grpc.trace_exporter import OTLPSpanExporter

👍1

💡1

Understanding Llamaindex Endpoint Usage: /v1/traces Explained | Arize AI Community

Roger Y.
·
Here’s a brief description of the ports. The error message in your screenshot mentions gRPC, so the correct port for that is 4317 and is without v1/traces. The v1/traces endpoint is a REST endpoint behind the 6006 port.
👍1

Roger Y.

when you specify the exporter, there are two ways: HTTP or gRPC

from opentelemetry.exporter.otlp.proto.http.trace_exporter import OTLPSpanExporter

from opentelemetry.exporter.otlp.proto.grpc.trace_exporter import OTLPSpanExporter

👍1

💡1