references/autogen.md
AutoGen LLM analytics installation - Docs
-
1
Install the PostHog SDK
Required
Setting up analytics starts with installing the PostHog SDK. The AutoGen integration uses PostHog's OpenAI wrapper since AutoGen uses OpenAI under the hood.
pip install posthog -
2
Install AutoGen
Required
Install AutoGen with the OpenAI extension. PostHog instruments your LLM calls by wrapping the OpenAI client that AutoGen uses internally.
pip install "autogen-agentchat" "autogen-ext[openai]" -
3
Initialize PostHog and AutoGen
Required
Initialize PostHog with your project token and host from your project settings, then create a PostHog OpenAI wrapper and pass it to AutoGen's
OpenAIChatCompletionClient.import asyncio from posthog.ai.openai import OpenAI from posthog import Posthog from autogen_agentchat.agents import AssistantAgent from autogen_ext.models.openai import OpenAIChatCompletionClient posthog = Posthog( "<ph_project_token>", host="https://us.i.posthog.com" ) openai_client = OpenAI( api_key="your_openai_api_key", posthog_client=posthog, ) model_client = OpenAIChatCompletionClient( model="gpt-4o", openai_client=openai_client, )How this works
AutoGen's
OpenAIChatCompletionClientaccepts a custom OpenAI client via theopenai_clientparameter. PostHog'sOpenAIwrapper is a proper subclass ofopenai.OpenAI, so it works directly. PostHog captures$ai_generationevents automatically without proxying your calls. -
4
Run your agents
Required
Use AutoGen as normal. PostHog automatically captures an
$ai_generationevent for each LLM call made through the wrapped OpenAI client.agent = AssistantAgent("assistant", model_client=model_client) async def main(): result = await agent.run(task="Say 'Hello World!'") print(result) await model_client.close() asyncio.run(main())You can expect captured
$ai_generationevents to have the following 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) | | [...] | See full list of properties |
-
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 LLM analytics, you should see rows of data appear in the Traces and Generations tabs.
LLM generations in PostHogLLM generations in PostHog
-
5
Next steps
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 | Learn the basics of how LLM calls become events in PostHog. | | Generations | Read about the $ai_generation event and its properties. | | Traces | Explore the trace hierarchy and how to use it to debug LLM calls. | | Spans | Review spans and their role in representing individual operations. | | Anaylze LLM performance | Learn how to create dashboards to analyze LLM performance. |
Community questions
Ask a question
Was this page useful?
HelpfulCould be better