Skip to content

Quickstart: LangGraph

Use the traces your LangGraph agent emits to test its behavior in Mibo. You instrument an order-support graph with OpenInference, export one trace over OpenTelemetry, and write your first tool-call test.

  • A Mibo workspace whose owner has verified their email.
  • Python 3.14 and uv.
  • An OpenAI API key for the model in this example.

Tested November 21, 2026 with Python 3.14.9 and the package versions pinned below.

If you own the workspace, create an API key in Settings and copy it. Mibo shows the key only once. If you’re a workspace member, ask the owner for a key.

This example sets service.name to langgraph-support. A workspace key lets Mibo create an Agent with that name on the first trace. A key scoped to one Agent sends traces to that Agent. See trace routing.

Run these commands in a new project directory.

Terminal window
uv venv --python 3.14
uv pip install langgraph==1.2.24 langchain-core==1.8.4 langchain-openai==1.8.5 \
openinference-instrumentation-langchain==0.1.89 opentelemetry-sdk==1.45.2 \
opentelemetry-exporter-otlp-proto-http==1.45.2
export MIBO_API_KEY='<YOUR_MIBO_API_KEY>'
export OPENAI_API_KEY='<YOUR_OPENAI_API_KEY>'
export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=https://api.mibo-ai.com/public/traces
export OTEL_SERVICE_NAME=langgraph-support

The LangChain OpenInference instrumentor captures LangGraph runs, including LangChain model and tool calls. If your app already emits OpenLLMetry traces, you can use the exporter in the OpenLLMetry quickstart.

Save the following as agent.py.

import asyncio
import os
from langchain_core.messages import AIMessage, HumanMessage
from langchain_core.tools import tool
from langchain_openai import ChatOpenAI
from langgraph.graph import START, MessagesState, StateGraph
from langgraph.prebuilt import ToolNode, tools_condition
from openinference.instrumentation.langchain import LangChainInstrumentor
from opentelemetry.exporter.otlp.proto.http.trace_exporter import OTLPSpanExporter
from opentelemetry.sdk.resources import Resource
from opentelemetry.sdk.trace import TracerProvider
from opentelemetry.sdk.trace.export import BatchSpanProcessor
provider = TracerProvider(
resource=Resource.create({"service.name": os.environ["OTEL_SERVICE_NAME"]}),
)
provider.add_span_processor(
BatchSpanProcessor(
OTLPSpanExporter(
endpoint=os.environ["OTEL_EXPORTER_OTLP_TRACES_ENDPOINT"],
headers={"x-api-key": os.environ["MIBO_API_KEY"]},
timeout=10,
)
)
)
LangChainInstrumentor().instrument(tracer_provider=provider)
@tool
async def lookup_order(order_id: str) -> dict[str, str]:
"""Look up an order by ID."""
return {"order_id": order_id, "status": "shipped", "eta": "Friday"}
model = ChatOpenAI(model="gpt-4o-mini", timeout=20, max_retries=0).bind_tools(
[lookup_order]
)
async def call_model(state: MessagesState) -> dict[str, list[AIMessage]]:
return {"messages": [await model.ainvoke(state["messages"])]}
async def main() -> None:
builder = StateGraph(MessagesState)
builder.add_node("assistant", call_model)
builder.add_node("tools", ToolNode([lookup_order]))
builder.add_edge(START, "assistant")
builder.add_conditional_edges("assistant", tools_condition)
builder.add_edge("tools", "assistant")
agent = builder.compile(name="support_agent")
result = await agent.ainvoke(
{"messages": [HumanMessage(content="Use lookup_order to check order A-1042.")]},
config={"recursion_limit": 5},
)
print(result["messages"][-1].text)
try:
asyncio.run(main())
finally:
provider.force_flush()
provider.shutdown()

Run the script.

Terminal window
uv run --no-project python agent.py

The script prints the model’s reply, for example Your order A-1042 has shipped and should arrive on Friday. Before the script exits, force_flush() exports buffered spans and shutdown() closes the provider.

Open Traces and select the Agent that received the trace by its current name. If Mibo created the Agent for this example, its initial name is langgraph-support. Open the order trace. If the model called lookup_order, it appears under What the agent did. Click View raw trace data to inspect the ChatOpenAI model spans.

  1. Wait for the order trace to finish, then click Create test from this trace.
  2. Open Draft if the editor shows tabs. Set Name to Looks up the order and clear Checks a trace when so the test checks each new trace for this Agent.
  3. Keep the Tool call check. If the draft omits it, choose Tool call from Does check. Set Tool name to lookup_order and select Must call. Remove the other checks and click Save test.
  4. Run the script again. Open the new trace on Traces and look under Test results. The check passes when the trace records a call to lookup_order.
Data OpenInference attributes
User input and final reply llm.input_messages.* and llm.output_messages.*
Requested model llm.invocation_parameters or llm.model_name
Tool name and result tool.name and output.value on the tool span
Tool arguments The tool_call.function.arguments field of the model’s indexed output message

OpenInference records this tool’s single string input as plain text on the tool span. The model’s message carries the structured arguments. Use the tool name for this check. Review Data handling before sending traces that contain personal data.

Problem Likely cause Solution
404 or connection error Wrong host or path, such as /public/traces/v1/traces Set the full traces endpoint to https://api.mibo-ai.com/public/traces.
KeyError: 'MIBO_API_KEY' or HTTP 401 Missing, invalid, or revoked key Set MIBO_API_KEY before running the script. Confirm that the exporter sends it as x-api-key. Ask the workspace owner to check whether the key is active.
HTTP 401 with API_KEY_EXPIRED in the message The API key expired Set MIBO_API_KEY to an active key and rerun the script.
Export fails with a gRPC transport error The exporter uses OTLP/gRPC Import the exporter from opentelemetry.exporter.otlp.proto.http.trace_exporter for OTLP/HTTP protobuf.
KeyError: 'OTEL_SERVICE_NAME' or HTTP 400 with a message beginning OTLP traces need the 'service.name' resource attribute OTEL_SERVICE_NAME is unset, or Mibo can’t infer the Agent from the exported resource Set OTEL_SERVICE_NAME to the Agent’s service name and pass it as a resource attribute as shown above.
The script prints a reply but no trace appears The process exits with spans still buffered Call provider.force_flush() after the graph finishes and provider.shutdown() before exit. Check exporter errors if the trace is still missing.
403 AGENT_LIMIT_REACHED Your plan has reached its Agent limit Use an existing Agent or free capacity for a new one. See Agent limit reached.
HTTP 403 with “Monthly trace ingestion limit reached” in the message Your workspace has used its monthly trace quota Wait for the next usage period or upgrade. Once capacity returns, rerun the script or resend the rejected payload.
Export succeeds but the trace is hidden or tool calls are missing Content capture is off, or the instrumentation emits an unsupported set of attributes Check your capture settings and the supported trace dialects. Use OpenInference or OpenLLMetry.