Disbale Tracing for some Langchain Components

[DRXD1000]

Hello Guys,

i am using the default Langchain tool

LangChainInstrumentor().instrument()

And i am sending Base64 as Metadata in my retriever. But this consumes a lot of memory in the traces. Is there a way to disable the tracing for some components of a langchain chain /graph?

THX!

[dosubot[bot]]

Yes, you can disable tracing for specific components of a Langchain chain/graph using the suppress_tracing context manager. Here is an example:

from phoenix.trace import suppress_tracing

with suppress_tracing():
    # Code running inside this block doesn't generate traces.
    # For example, running LLM evals here won't generate additional traces.
    ...
# Tracing will resume outside the block.
...

Additionally, to disable tracing permanently for the LangChain instrumentor, you can call the .uninstrument() method:

LangChainInstrumentor().uninstrument()

This will stop tracing indefinitely for the LangChain components ^[1][2].

To continue talking to Dosu, mention @dosu.

[dosubot[bot]]

Yes, you can exclude the metadata of your retriever for all steps by popping the METADATA attribute from the retriever_attributes dictionary. Here is an example:

# Ignore metadata since LC adds a bunch of unstable metadata
retriever_attributes.pop(METADATA, None)
assert retriever_attributes == {}

This code effectively removes the METADATA attribute from the retriever's attributes, ensuring that the metadata is excluded ^[1][2].

To continue talking to Dosu, mention @dosu.

[mikeldking]

@DRXD1000 were you able to get it resolved? Curious why there is a large payload in your metadata. Are you leveraging LangChain metadata to pass data between components?

If you roughly know the size of the payload, you can suppress all attributes that are larger than a certain size using openTelemetry environment variables. https://opentelemetry.io/docs/specs/otel/common/#configurable-parameters

[DRXD1000]

@mikeldking i have a langgraph implementation where the retriever supplies images as base64 in the metadata (Demo Application). And the size of the base64 strings breaks the phoenix container. I will probably switch to another method of storing the images. Right now i cant find a way to exclude the document metadata in the traces.

[mikeldking]

I see - that's unfortunate that it's in metadata. We do support striping images but only if it's in the messages:

from openinference.instrumentation import TraceConfig
config = TraceConfig(
    hide_inputs=hide_inputs,
    hide_outputs=hide_outputs,
    hide_input_messages=hide_input_messages,
    hide_output_messages=hide_output_messages,
    hide_input_images=hide_input_images,
    hide_input_text=hide_input_text,
    hide_output_text=hide_output_text,
    base64_image_max_length=base64_image_max_length,
)
tracer_provider=...
# This example uses the OpenAIInstrumentor, but it works with any of our auto instrumentors
OpenAIInstrumentor().instrument(tracer_provider=tracer_provider, config=config)

Let us know if there's anything we can do to help.

[DRXD1000]

Oh that is very nice! The answer of dosu bot was actually also very good and with that i will probably integrate a separate call for images without tracing or use the image striping as you proposed. Thank you very much for your time :)