LangGraph AI Observability installation

Let AI instrument your LLM calls for you

Skip the manual setup — run this in your project and the wizard installs the SDK and wires up AI Observability for you.

Learn more
PostHog Wizard hedgehog

Contents

  1. Install dependencies

    Required
    Full working examples

    See the complete Node.js and Python examples on GitHub.

    Install the PostHog SDK and LangGraph with OpenAI.

    pip install posthog langgraph langchain-core langchain-openai
  2. Configure PostHog

    Required

    Create a PostHog client once, then build a callback handler for each request or conversation. distinct_id ties each call to a user, and $ai_session_id groups calls in one conversation.

    from posthog import Posthog
    from posthog.ai.langchain import CallbackHandler
    posthog = Posthog("<ph_project_token>", host="https://us.i.posthog.com")
    def create_handler(user_id: str, session_id: str) -> CallbackHandler:
    return CallbackHandler(
    client=posthog,
    distinct_id=user_id,
    properties={"$ai_session_id": session_id},
    )

    Note: If you want to capture LLM events anonymously, omit distinct_id/distinctId when constructing the handler. See our docs on anonymous vs identified events to learn more.

  3. Run your graph

    Required

    Attach the handler through config when you invoke the graph, inside the function that handles a turn. Because create_react_agent runs the turn as a single root run, PostHog nests each tool call as an $ai_span under the trace automatically, with real latency.

    from langgraph.prebuilt import create_react_agent
    from langchain_openai import ChatOpenAI
    from langchain_core.tools import tool
    @tool
    def get_weather(city: str) -> str:
    """Get the weather for a given city."""
    return f"It's always sunny in {city}!"
    model = ChatOpenAI(api_key="your_openai_api_key")
    agent = create_react_agent(model, tools=[get_weather])
    def ask(user_input: str, user_id: str, conversation_id: str) -> str:
    handler = create_handler(user_id=user_id, session_id=conversation_id)
    result = agent.invoke(
    {"messages": [{"role": "user", "content": user_input}]},
    config={"callbacks": [handler]},
    )
    return result["messages"][-1].content
    print(ask("What's the weather in Paris?", "user_123", "conversation-abc"))

    PostHog automatically captures an $ai_generation event along with these properties:

    PropertyDescription
    $ai_modelThe specific model, like gpt-5-mini or claude-4-sonnet
    $ai_latencyThe latency of the LLM call in seconds
    $ai_time_to_first_tokenTime to first token in seconds (streaming only)
    $ai_toolsTools and functions available to the LLM
    $ai_inputList of messages sent to the LLM
    $ai_input_tokensThe number of tokens in the input (often found in response.usage)
    $ai_output_choicesList of response choices from the LLM
    $ai_output_tokensThe number of tokens in the output (often found in response.usage)
    $ai_total_cost_usdThe total cost in USD (input + output)
    [...]See full list of properties

    The handler also builds a trace hierarchy automatically based on how you structure your graph. Pass the same $ai_session_id to every handler you construct for a conversation, to group its calls into one session. Pass trace_id/traceId too, to control the top-level trace ID instead of letting PostHog generate one.

  4. Verify traces and generations

    Recommended
    Confirm LLM events are being sent to PostHog

    Let's make sure LLM events are being captured and sent to PostHog. Under AI Observability, you should see rows of data appear in the Traces and Generations tabs.


    LLM generations in PostHog
    Check for LLM events in PostHog
  5. Next steps

    Recommended

    Now that you're capturing AI conversations, continue with the resources below to learn what else AI Observability enables within the PostHog platform.

    ResourceDescription
    BasicsLearn the basics of how LLM calls become events in PostHog.
    GenerationsRead about the $ai_generation event and its properties.
    TracesExplore the trace hierarchy and how to use it to debug LLM calls.
    SpansReview spans and their role in representing individual operations.
    Anaylze LLM performanceLearn how to create dashboards to analyze LLM performance.

Community questions

Was this page useful?