Adding Multiple Span Processors with LangChain Instrumentor in Python | Arize AI Community

Arize AI Community Icon

Adding Multiple Span Processors with LangChain Instrumentor in Python | Arize AI Community

RunLLM
APP
·
To export spans to multiple destinations using the LangChainInstrumentor, you need to ensure that multiple SpanProcessor instances are added to the TracerProvider. The add_span_processor method in your code seems to override the default processor, which is why you're facing issues. You can add multiple span processors by directly calling add_span_processor for each processor you want to add.Here's an example of how you can achieve this: LBKSfrom opentelemetry.sdk.trace.export import ConsoleSpanExporter, SimpleSpanProcessor from opentelemetry.exporter.otlp.proto.http.trace_exporter import OTLPSpanExporter from openinference.instrumentation.langchain import LangChainInstrumentor from phoenix.otel import registerLBKS# Phoenix and OpenTelemetry setup tracer_provider = register( project_name="default", endpoint="[http://localhost:6006/v1/traces](http://localhost:6006/v1/traces)" )LBKS# Add the console exporter console_exporter = ConsoleSpanExporter() console_processor = SimpleSpanProcessor(console_exporter) tracer_provider.add_span_processor(console_processor)LBKS# Add the OTLP exporter otlp_exporter = OTLPSpanExporter(endpoint="[http://localhost:6006/v1/traces](http://localhost:6006/v1/traces)") otlp_processor = SimpleSpanProcessor(otlp_exporter) tracer_provider.add_span_processor(otlp_processor)LBKS# Instrument LangChain LangChainInstrumentor().instrument(tracer_provider=tracer_provider)LBKSThis setup ensures that spans are exported both to the console and to the specified OTLP endpoint. Would you like more detail on any specific part?Sources: - LangChain Instrumentation Example
💡 Hint: Mention RunLLM in the thread for followups.
John G.
·
abhijit h. taking a look now!
1
abhijit h.
·
as the bot suggested, that worked.
abhijit h.
·
with a minor change.
John G.
·
Great to hear it! Just to be safe, the with_using_attributes piece may not be necessary depending on what you're doing. Just the approach of not using the register function and instead defining both span processors yourself is the key
abhijit h.
·
yup, agree John G., I removed the register function. Not sure why I was using that. Maybe I followed a example. Any advantages of using register function ?
John G.
·
It is our recommended approach at this point, since it makes the otel setup a lot easier. The function replaces a lot of the otel boilerplate, and does some other helpful things like automatically detect whether to use HTTP or GRPC to send the traces Your case here is a little more custom, so makes sense to go a level deeper
John G.
·
I'm not sure why we replace the span processor though. I'll have to check with the team on that one
abhijit h.
·
Thanks John G., yeah that would be good to know, why remove the default span processor when adding a new one. Or atleast give a option not to replace it, because the OTEL allows to have multiple span processors, so phoenix contradicts that ideology of OTEL. Thanks
abhijit h.
·
Appreciate the help.
John G.
·
Filed it as an issue since it would be good to have a longer term record of the answer
🙌1