PostHog - OpenSRE Documentation

Overview

OpenSRE stores your PostHog project credentials for REST API access (project metadata and correlation during investigations). Configure with opensre integrations setup posthog or POSTHOG_* environment variables. This REST integration does not register investigation tools. For agent tools during investigations (analytics, feature flags, HogQL), use PostHog (MCP).

What you want	Use	Setup
Store PostHog REST credentials for your project	PostHog (this page)	`opensre integrations setup posthog` or env vars below
Let the agent explore PostHog during incidents	PostHog (MCP)	`opensre integrations setup posthog_mcp` or onboarding wizard
OpenSRE’s own product usage telemetry	Built-in analytics	Controlled by `OPENSRE_NO_TELEMETRY` — not your PostHog project

Prerequisites

A PostHog account (US, EU, or self-hosted)
Your PostHog project ID
A personal API key with read access to that project — see PostHog personal API keys

Setup

Option 1: Interactive CLI

opensre integrations setup posthog

Or run the onboarding wizard and select PostHog under Observability. You will be prompted for:

Project ID — from PostHog project settings
Personal API key (phx_...) — Personal API keys with read access
API base URL — defaults to US SaaS (https://us.i.posthog.com); use https://eu.i.posthog.com for EU

On success, credentials are saved to your integration store and synced to .env.

Option 2: Environment variables

POSTHOG_PROJECT_ID=your_project_id
POSTHOG_PERSONAL_API_KEY=phx_your_personal_api_key
POSTHOG_BASE_URL=https://us.i.posthog.com           # optional — US SaaS default
POSTHOG_TIMEOUT_SECONDS=15.0                        # optional

Credentials

Variable	Default	Description
`POSTHOG_PROJECT_ID`	—	Required. Your PostHog project ID
`POSTHOG_PERSONAL_API_KEY`	—	Required. Personal API key for the project
`POSTHOG_BASE_URL`	`https://us.i.posthog.com`	API base URL (`https://eu.i.posthog.com` for EU, or your self-hosted origin)
`POSTHOG_TIMEOUT_SECONDS`	`15.0`	HTTP timeout in seconds

Get the project ID from PostHog project settings. Create a personal API key (phx_...) with read access — see PostHog personal API keys.

Investigation tools

This REST integration does not register investigation tools. For agent tools during investigations (analytics, feature flags, HogQL), use PostHog (MCP).

Verify

opensre integrations verify posthog

A successful check prints PostHog validated. For the MCP integration, use opensre integrations verify posthog_mcp instead.

Troubleshooting

Symptom	Fix
Authentication failed (401)	Check `POSTHOG_PERSONAL_API_KEY` is valid and has read access
Project not found (404)	Confirm `POSTHOG_PROJECT_ID` matches the instance in `POSTHOG_BASE_URL`
Verify says not configured	Both `POSTHOG_PROJECT_ID` and `POSTHOG_PERSONAL_API_KEY` must be set

Security

Use a dedicated personal API key with the minimum read permissions needed
Store credentials in environment variables or a secret manager — not in source code
Rotate keys periodically

​Overview

​Prerequisites

​Setup

​Option 1: Interactive CLI

​Option 2: Environment variables

​Credentials

​Investigation tools

​Verify

​Troubleshooting

​Security