Chapter 150 · LLM Analytics Setup
Subchapter 150.17
references/langchain.mdMarkdown7 KBView on GitHub
Required
Setting up analytics starts with installing the PostHog SDK for your language. LLM analytics works best with our Python and Node SDKs.
PostHog AI
pip install posthognpm install @posthog/ai posthog-node2
Required
Install LangChain. The PostHog SDK instruments your LLM calls by wrapping LangChain. The PostHog SDK does not proxy your calls.
PostHog AI
pip install langchain openai langchain-openainpm install langchain @langchain/core @langchain/openai @posthog/aiProxy note
These SDKs do not proxy your calls. They only fire off an async call to PostHog in the background to send the data. You can also use LLM analytics with other SDKs or our API, but you will need to capture the data in the right format. See the schema in the manual capture section (opens in a new tab) for more details.
3
Required
Initialize PostHog with your project token and host from your project settings (opens in a new tab), then pass it to the LangChain CallbackHandler wrapper. Optionally, you can provide a user distinct ID, trace ID, PostHog properties, groups (opens in a new tab), and privacy mode.
PostHog AI
from posthog.ai.langchain import CallbackHandler
from langchain_openai import ChatOpenAI
from langchain_core.prompts import ChatPromptTemplate
from posthog import Posthog
posthog = Posthog(
"<ph_project_token>",
host="https://us.i.posthog.com"
)
callback_handler =
import { PostHog } from 'posthog-node';
import { LangChainCallbackHandler } from '@posthog/ai';
import { ChatOpenAI } from '@langchain/openai';
import { ChatPromptTemplate } from '@langchain/core/prompts';
const phClient = new PostHog(
'<ph_project_token>',
Note: If you want to capture LLM events anonymously, don’t pass a distinct ID to the
CallbackHandler. See our docs on anonymous vs identified events (opens in a new tab) to learn more.
4
Required
When you invoke your chain, pass the callback_handler in the config as part of your callbacks:
PostHog AI
prompt = ChatPromptTemplate.from_messages([
("system", "You are a helpful assistant."),
("user", "{input}")
])
model = ChatOpenAI(openai_api_key="your_openai_api_key")
chain = prompt | model
# Execute the chain with the callback handler
response = chain.invoke(
{"input": "Tell me a joke about programming"},
config={"callbacks": [callback_handler]}
)
print(response.content)const prompt = ChatPromptTemplate.fromMessages([
["system", "You are a helpful assistant."],
["user", "{input}"]
]);
const model = new ChatOpenAI({
apiKey: "your_openai_api_key"
});
const chain = prompt.pipe
PostHog automatically captures an $ai_generation event along with these properties:
| Property | Description |
|---|---|
| $ai_model | The specific model, like gpt-5-mini or claude-4-sonnet |
| $ai_latency | The latency of the LLM call in seconds |
| $ai_time_to_first_token | Time to first token in seconds (streaming only) |
| $ai_tools | Tools and functions available to the LLM |
| $ai_input | List of messages sent to the LLM |
| $ai_input_tokens | The number of tokens in the input (often found in response.usage) |
| $ai_output_choices | List of response choices from the LLM |
| $ai_output_tokens | The number of tokens in the output (often found in response.usage) |
| $ai_total_cost_usd | The total cost in USD (input + output) |
| […] (opens in a new tab) | See full list (opens in a new tab) of properties |
It also automatically creates a trace hierarchy based on how LangChain components are nested.
Recommended
Confirm LLM events are being sent to PostHog
Let’s make sure LLM events are being captured and sent to PostHog. Under LLM analytics, you should see rows of data appear in the Traces and Generations tabs.


5
Recommended
Now that you’re capturing AI conversations, continue with the resources below to learn what else LLM Analytics enables within the PostHog platform.
| Resource | Description |
|---|---|
| Basics (opens in a new tab) | Learn the basics of how LLM calls become events in PostHog. |
| Generations (opens in a new tab) | Read about the $ai_generation event and its properties. |
| Traces (opens in a new tab) | Explore the trace hierarchy and how to use it to debug LLM calls. |
| Spans (opens in a new tab) | Review spans and their role in representing individual operations. |
| Anaylze LLM performance (opens in a new tab) | Learn how to create dashboards to analyze LLM performance. |
Ask a question
HelpfulCould be better