ޠj "SrSSKJr SSKrSSKrSSKJrJrJrJ r J r SSK J r SSKJr SSKJrJr \(aSS KJrJr SS KJrJr \R2"\5r/S QrSS jrSS jrSSjrSS.SSjjr SSSjjr!g)z(OpenTelemetry integration for LangSmith.) annotationsN) TYPE_CHECKINGAnyOptionalUnioncast)utils)Client)otel_safe_attribute_value set_langsmith_metadata_attribute)Span SpanContext) OtelExporterOtelSpanProcessor) configurerr"langsmith_run_id_from_otel_span_idget_langsmith_run_url_for_spanr r c^US;aSSKJn [X5$[S[<SU<35e)zHLazily import processor exports so offline helpers stay dependency-free.)rrr ) processorzmodule z has no attribute )rgetattrAttributeError__name__)namers ^/var/www/html/gaurav/venv/lib/python3.13/site-packages/langsmith/integrations/otel/__init__.py __getattr__r s2 44y'' 78,.@I JJc[U[5(aBS[U5s=::aS::dO [S[U535eUR SS5nOy[U[ 5(a [ S5e[U[5(a-SUs=::aS:d O [S5eURSS5nO[ S [U535eUS :Xa [S 5e[R"US 9$) aMap an OpenTelemetry span ID to its LangSmith run ID. The LangSmith backend derives a run's UUID from the OTel span ID during ingest: the span-ID bytes are copied right-aligned into a 16-byte, zero-padded buffer, and those bytes become the run UUID. This mapping is deterministic and fully offline: it makes no network request and does not require `opentelemetry` to be installed. The span ID to run ID relationship is fixed by the server's ingest rule, so the run ID is stable regardless of when (or whether) ingest has completed. Args: span_id: The OTel span ID, either as an `int` (as returned by `span.get_span_context().span_id`) or as raw `bytes` (8 to 16 bytes; left-padded with zeros to 16 bytes). Returns: The LangSmith run ID as a `uuid.UUID`. r z&span_id bytes must be 1-16 bytes, got z&span_id must be int or bytes, got boollz+span_id int must be a non-zero 64-bit valuebigz"span_id must be int or bytes, got sz6span_id is all-zero, which is not a valid OTel span ID)bytes) isinstancer#len ValueErrorrjustbool TypeErrorintto_bytestypeuuidUUID)span_idraws rrr)s('5!!CL&B&Ec'l^TU UmmB( GT " "@AA GS ! !G'w'JK Kr5)Extract the integer span ID from an OTel span or span context.r)r)opentelemetry.tracerr$get_span_contextr/)spanrctxs r_extract_span_idr6Ps:(%/%;%;$   !C ;;BFC ;;r)clientcU=(d [5n[[U55nURSUR 5SUSUS3$)aBuild the LangSmith run URL for a native OpenTelemetry span. Useful when your application creates and exports OTel spans to LangSmith and wants to surface a run URL immediately, without polling or waiting for asynchronous OTel ingest to complete. The span ID to run ID mapping is deterministic and offline (see `langsmith_run_id_from_otel_span_id`). The returned URL is "eventually valid": it points at the run that will materialize once OTel ingest finishes, which may not have happened yet at the time of the call. Network usage: - The span to run ID mapping is fully offline. - Resolving `tenant_id` and `host_url` for the URL uses `client` (a default `Client` is constructed if none is given). Args: span: An OTel span or span context. project_id: The LangSmith project (session) ID. client: Optional `Client` used to resolve tenant and host URL. Returns: The full LangSmith run URL. z/o/z /projects/p/z/r/z ?poll=true)r rr6 _host_url_get_tenant_id)r4 project_idr7run_ids rrrXsY< vxF /0@0F GF    C 5 5 78 ZLQ HJ rcSSKJn SSKJn SSKJnJnJn [XCR55nUR[5n [X5(aO[U S5(a>[[UU 5RU5(aU"5n URU 5 O[ R#S5 gU=(d [$R&"S5nU(dgU=(d [$R("5nS S KJn U "XUS 9n U R/U 5 g ![0a n [ R#S U 5 Sn A gSn A ff=f)aConfigure OpenTelemetry with LangSmith as the `TracerProvider`. Initializes OpenTelemetry with LangSmith as the primary and only `TracerProvider`. Usage: >>> from langsmith.integrations.otel import configure >>> configure( # doctest: +SKIP ... api_key="your-api-key", project_name="your-project" ... ) Using environment variables: >>> # Set LANGSMITH_API_KEY and LANGSMITH_PROJECT >>> configure() # Will use env vars # doctest: +SKIP !!! warning This function is only for when LangSmith is your ONLY OpenTelemetry source. It sets the global TracerProvider, which can only be done once per application. This function will fail if OpenTelemetry is already initialized with another `TracerProvider` (you cannot override an existing `TracerProvider`). If you already have OpenTelemetry set up with other tools, use `OtelSpanProcessor` directly to add LangSmith to your existing setup: !!! example "Adding LangSmith to existing OTEL setup" ```python from opentelemetry import trace from langsmith.integrations.otel.processor import OtelSpanProcessor # Use your existing provider (already initialized) provider = trace.get_tracer_provider() # Add LangSmith processor to existing provider langsmith_processor = OtelSpanProcessor( api_key="your-api-key", project="your-project" ) provider.add_span_processor(langsmith_processor) ``` Args: api_key: LangSmith API key. Defaults to `LANGSMITH_API_KEY` env var. project_name: Project name. Defaults to `LANGSMITH_PROJECT` env var. SpanProcessor: Span processor class to use. Defaults to `BatchSpanProcessor`. Returns: `True` if configuration succeeded, `False` if `TracerProvider` already exists. r)trace)TracerProvider) NoOpTracer ProxyTracerProxyTracerProvider_tracerzOpenTelemetry TracerProvider is already set. Cannot override existing TracerProvider. Use OtelSpanProcessor directly to add LangSmith to your existing provider instead.FNr )r)api_keyproject SpanProcessorTz(Failed to initialize Otel for LangSmith:) opentelemetryr>opentelemetry.sdk.tracer?r2r@rArBrget_tracer_provider get_tracerrr$hasattrrCset_tracer_providerloggerwarningls_utils get_api_keyget_tracer_projectrradd_span_processor Exception)rD project_namerFr>r?r@rArBexisting_providertracerproviderrres rrr~sl/':TT 1J1J1LM"--h7 ( > > **' &'H  % %h / NNO  7X11$7#Dx'B'B'D 0%  ##I. A1Es$B8D;&D"rhs." <<'#O5:   8 $ K$ N $ # "##  #  #N""&$(e ee"e er