i8ddlZddlmZmZmZmZddlmZddlm Z ddl m Z ddl m Z er2ddlmZddlmZdd lmZdd lmZdd lmZdd lmZeZeZeeefZeZneZeZeZeZeZ dd lmZd ZGddeZy#e$rdZYwxYw)N) TYPE_CHECKINGAnyOptionalUnion)verbose_logger)_utils)ArizeOTELAttributes)ArizePhoenixConfigTracerProvider)SpanSpanKind) OpenTelemetry)OpenTelemetryConfig)Protocolz https://otlp.arize.com/v1/tracesceZdZdZdZdZdedeefdZ e defdZ e dee fd Z d Zd Zd Ze defd ZdZy)ArizePhoenixLoggera+ Arize Phoenix logger that sends traces to a Phoenix endpoint. Creates its own dedicated TracerProvider so it can coexist with the generic ``otel`` callback (or any other OTEL-based integration) without fighting over the global ``opentelemetry.trace`` TracerProvider singleton. cddlm}ddlm}||j d|_||_y||j|j}|j|j|j d|_||_tjd|jj|jjy)a Override to always create a *private* TracerProvider for Arize Phoenix. The base ``OpenTelemetry._init_tracing`` falls back to the global TracerProvider when one already exists. That causes whichever integration initialises second to silently reuse the first one's exporter, so spans only reach one destination. By creating our own provider we guarantee Arize Phoenix always gets its own exporter pipeline, regardless of initialisation order. rr rNlitellm)resourcezOArizePhoenixLogger: Created dedicated TracerProvider (endpoint=%s, exporter=%s))opentelemetry.sdk.tracer opentelemetry.tracer get_tracertracer span_kind_get_litellm_resourceconfigadd_span_processor_get_span_processorrdebugendpointexporter)selftracer_providerr rproviders y/Users/manta/Documents/Projects/TheRoad-I1/.venv/lib/python3.12/site-packages/litellm/integrations/arize/arize_phoenix.py _init_tracingz ArizePhoenixLogger._init_tracing1s ;0  &)44Y?DK%DN "4+E+Edkk+RS##D$<$<$>?)))4 ! ) KK KK  cy)z Override: Arize Phoenix should NOT overwrite the proxy's ``open_telemetry_logger``. That attribute is reserved for the primary ``otel`` callback which handles proxy-level parent spans. N)r$s r'"_init_otel_logger_on_litellm_proxyz5ArizePhoenixLogger._init_otel_logger_on_litellm_proxyRs r)span response_objc2tj|||y)N)rset_arize_phoenix_attributes)r$r-kwargsr.s r'set_attributesz!ArizePhoenixLogger.set_attributesZs77flSr)cddlm}tj|||tt j |}|r ||d|yt j}|jr||d|jy)Nr)safe_set_attributezopeninference.project.name) Elitellm.integrations.opentelemetry_utils.base_otel_llm_obs_attributesr4rr2r r_get_dynamic_project_nameget_arize_phoenix_config project_name)r-r1r.r4dynamic_project_namers r'r0z/ArizePhoenixLogger.set_arize_phoenix_attributes^s{  dFL:MN 2KKFS  t%ACW X  (@@BF"""68K8K r)returnc|jd}t|tr?|jd}t|tr|jd}|r t|S|jd}t|tr|jdxsi}ni}t|tr|jd}|r t|Sy)z Retrieve dynamic Phoenix project name from request metadata. Users can set `metadata.phoenix_project_name` in their request to route traces to different Phoenix projects dynamically. standard_logging_objectmetadataphoenix_project_namelitellm_paramsN)get isinstancedictstr)r1standard_logging_payloadr=r8r?s r'r6z,ArizePhoenixLogger._get_dynamic_project_namets$*::.G#H . 5/33J?H(D)'||,BC |,, $45 nd +%))*5;HH h %#<<(>?L<((r)cddlm}|jdixsi}|jdixsi}|jdixsi}|jdr|j|nd}t |}|r||jd |jd }|j j d ||j|nd||jj } |j| } | | fS|dfS) u Build a trace context for Phoenix's dedicated TracerProvider. The base ``_get_span_context`` returns parent spans from the global TracerProvider (the ``otel`` callback). Those spans live on a *different* TracerProvider, so they won't appear in Phoenix — using them as parents just creates broken links. Instead we: 1. Honour an incoming ``traceparent`` HTTP header (distributed tracing). 2. In proxy mode, create our *own* parent span on Phoenix's tracer so the hierarchy is visible end-to-end inside Phoenix. 3. In SDK (non-proxy) mode, just return (None, None) for a root span. r)tracer?proxy_server_requestheaders traceparent)rHN start_timeapi_call_start_timelitellm_proxy_request)namerJcontextkind) opentelemetryrFr@get_traceparent_from_headerboolr start_span_to_nsrSERVERset_span_in_context) r$r1rFr?rGrHtraceparent_ctx is_proxy_modestart_time_val parent_spanctxs r'_get_phoenix_contextz'ArizePhoenixLogger._get_phoenix_contexts ($4b9?R-112H"MSQS&**9b9?R {{=)  , ,W , =  12 $ZZ fjjAV6WXN++00,!- ;;~6'^^** 1K++K8C # #$$r)cddlm}m}tjd||j |j |\}}|jj|j||j||} | j||j|j| |||j||||| | j|j||j!|||U|j||j|j||||j|j||j#|||||j j$r|j'||| yy)a Override to always create spans on ArizePhoenixLogger's dedicated TracerProvider. The base class's ``_get_span_context`` would find the parent span created by the ``otel`` callback on the *global* TracerProvider. That span is invisible in Phoenix (different exporter pipeline), so we ignore it and build our own hierarchy via ``_get_phoenix_context``. rStatus StatusCodez?ArizePhoenixLogger: Logging kwargs: %s, OTEL config settings=%srMrJrNend_timer1rNN)rr_r`rr!rr\rrS_get_span_namerT set_statusOKr2_maybe_log_raw_requestend_create_guardrail_span_record_metrics enable_events_emit_semantic_logs r$r1r.rJrcr_r`r[rZr-s r'_handle_successz"ArizePhoenixLogger._handle_successsc ; M  KK  44V<[{{%%$$V,{{:.&  z}}-. D&,7 ##FL*hPTU $++h/0 ##63#?  "  " "6*--#8 9    V\ B OOT[[%:O ; V\:xH ;; $ $  $ $V\4 @ %r)cddlm}m}tjd||j |j |\}}|jj|j||j||} | j||j|j| |||j| || j|j||j!|||i|j||j|j||||j|||j|j|yy) z Override to always create failure spans on ArizePhoenixLogger's dedicated TracerProvider. Mirrors ``_handle_success`` but sets ERROR status. rr^zIArizePhoenixLogger: Failure - Logging kwargs: %s, OTEL config settings=%sra)r-r1rbrdN)rr_r`rr!rr\rrSrerTrfERRORr2_record_exception_on_spanrirjrns r'_handle_failurez"ArizePhoenixLogger._handle_failures= ; W  KK  44V<[{{%%$$V,{{:.&  z//01 D&,7 &&D&@ $++h/0 ##63#?  "  " "6**:*:#; <    V\ B  * * F * K OOT[[%:O ; #r)ctjjdd}tjjdd}|sFtjjdd}tjjdd}|xs|}d}d}|rd|jdsd|vr d|vr|}d }nbd |vr|}d}n:d|vr4|j d r|d z}n|j d r|d}n|d}n|}d}nd}d}t j d|d}|d|}nd |vr tdtjjdd}t||||S)z Retrieves the Arize Phoenix configuration based on environment variables. Returns: ArizePhoenixConfig: A Pydantic model containing Arize Phoenix configuration. PHOENIX_API_KEYNPHOENIX_COLLECTOR_HTTP_ENDPOINTPHOENIX_COLLECTOR_ENDPOINT otlp_httpzgrpc://z:4317z /v1/traces otlp_grpczapp.phoenix.arize.comz/v1z/traces/z v1/traceszhttp://localhost:6006/v1/traceszKNo PHOENIX_COLLECTOR_ENDPOINT found, using default local Phoenix endpoint: zAuthorization=Bearer zMPHOENIX_API_KEY must be set when using Phoenix Cloud (app.phoenix.arize.com).PHOENIX_PROJECT_NAMEdefault)otlp_auth_headersprotocolr"r8) osenvironr@ startswithendswithrr! ValueErrorr )api_keycollector_endpoint grpc_endpoint http_endpointr"r~r}r8s r'r7z+ArizePhoenixLogger.get_arize_phoenix_configs**..!2D9ZZ^^,MtT!JJNN+GNMJJNN+LdSM!.!?- ( !,,Y7--,FX2X-&+.@@1H*H!);;)2259#5 #A+44S9&8%9#C&8%9#D1H&9H"H  ]^f]gh !  "7y A  $ 0_ zz~~&rs 66+-AG61,RGH.  D"MH DNHD !C@ @   s(A<<BB