Viewing trace details and latency in LangChain - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

Understanding trace output in LangChain

You run a LangChain chain with tracing enabled. What information will you see in the trace details?

LangChain

from langchain.chains import LLMChain
from langchain.llms import OpenAI
from langchain.callbacks import get_openai_callback

llm = OpenAI(temperature=0)
chain = LLMChain(llm=llm, prompt="Tell me a joke about {topic}.")

with get_openai_callback() as cb:
    result = chain.run(topic="cats")
    trace = cb

print(trace)

A The trace only shows the final output text without any timing or token usage info.

B The trace shows the prompt sent, tokens used, latency per request, and cost details.

C The trace shows only the raw API response JSON without prompt or latency info.

D The trace shows the prompt and output but no token usage or latency details.

💡 Hint

Think about what information helps you understand how long and costly the request was.

LangChain's callback tracing captures prompt text, token usage, latency, and cost details to help you analyze performance.

❓ state_output

intermediate

Latency measurement in LangChain callbacks

Which callback method in LangChain is responsible for measuring the latency of an LLM call?

A on_tool_end

B on_llm_start

C on_llm_end

D on_chain_end

💡 Hint

Latency is measured after the LLM finishes processing.

The on_llm_end callback is called when the LLM finishes, allowing measurement of elapsed time.

🔧 Debug

advanced

Diagnosing missing latency in trace output

You enabled tracing in LangChain but the latency field in the trace details is always zero. What is the most likely cause?

A The chain was run without the callback manager.

B The LLM model does not support latency reporting.

C The prompt template is missing required variables.

D The callback does not record start time before the LLM call begins.

💡 Hint

Latency requires measuring time before and after the call.

If the callback does not record the start time before the LLM call, latency calculation will be zero.

🧠 Conceptual

advanced

Interpreting trace latency in nested chains

In a LangChain setup with nested chains, how is latency reported in trace details for the outer chain compared to inner chains?

A Outer chain latency includes the total time of all inner chains plus its own processing time.

B Outer chain latency only shows its own processing time, excluding inner chains.

C Inner chains latency is aggregated and shown only in the outer chain trace.

D Latency is reported separately and cannot be summed across nested chains.

💡 Hint

Think about how nested calls add up in total time.

The outer chain's latency includes the time taken by all inner chains it calls plus its own overhead.

📝 Syntax

expert

Correct usage of LangChain tracing with async calls

Which code snippet correctly enables tracing and measures latency for an async LangChain chain call?

A

async with get_openai_callback() as cb:
    result = await chain.arun(input="hello")
    print(cb)

B

with get_openai_callback() as cb:
    result = await chain.arun(input="hello")
    print(cb)

C

async with get_openai_callback() as cb:
    result = chain.run(input="hello")
    print(cb)

D

with get_openai_callback() as cb:
    result = chain.run(input="hello")
    print(cb)

💡 Hint

Async calls require async context managers and await keywords.

For async chain calls, use async with and await to properly measure latency.