posthog▌

### PostHog Node.js Log Integration - Configure OpenTelemetry OTLP exporters to send log data directly to the PostHog ingestion endpoint. - Use environment variables for all sensitive configuration, including PostHog keys and OTLP endpoints. - Implement structured logging with key-value properties to enhance searchability and analysis within the PostHog platform.

### PostHog Java Log Ingestion - Integrate PostHog log ingestion into Java applications using the OpenTelemetry protocol and OTLP exporters. - Use environment variables for PostHog keys and endpoints instead of hardcoding sensitive configuration data. - Implement structured logging with key-value properties and add log export alongside existing logging infrastructure.

### PostHog Ruby on Rails Integration - Install the posthog-rails gem and use PostHog.init in an initializer to manage the client lifecycle automatically. - Securely store API keys using environment variables or Rails credentials instead of hardcoding them in your application. - Use class-level PostHog.capture and PostHog.identify methods to track events and associate users across backend and background jobs.

### PostHog Feature Flags for Ruby - Install the posthog-ruby gem and initialize the client using environment variables for API keys to ensure secure configuration. - Implement server-side flag evaluation to prevent UI flickering and use boolean flags as the default for simple feature toggling. - Always call client.shutdown in an ensure block for scripts and CLIs to prevent data loss and ensure proper event flushing.

### PostHog HogQL Query Reference - Access comprehensive schema documentation for core system models including cohorts, feature flags, error tracking, and data warehouse. - Utilize a library of optimized analytical query templates for trends, funnels, retention, user paths, and LLM trace analysis. - Reference HogQL-specific syntax, available functions, and extensions for advanced data manipulation and session replay analysis.

### Analyzing Experiment Session Replays - Retrieve experiment metadata and variant keys from the feature flag to ensure accurate filtering for each test group. - Construct session recording filters using the $feature_flag_called event and the specific $feature/<flag_key> property for each variant. - Compare session duration, activity metrics, and navigation paths across variants to provide qualitative insights on user behavior.

### PostHog Python Integration - Install the posthog package and initialize the Posthog() class with enable_exception_autocapture=True for automatic error tracking. - Use environment variables for API keys and register posthog_client.shutdown with atexit to ensure all events are flushed on exit. - Identify users via set() for person properties and never include PII like emails or names within capture() event properties.

### PostHog Android Integration - Initialize PostHog in the Application class onCreate method using environment variables for keys to ensure secure, early configuration. - Follow the provided example project patterns and ensure every activity includes an android:label for accurate screen view tracking. - Identify users during login and signup, passing session and distinct ID headers to maintain correlation across frontend and backend.

### PostHog LLM Analytics Integration - Integrate PostHog analytics into any LLM application using provider-specific guides or the manual capture fallback for custom setups. - Capture essential metrics including input/output tokens, model names, latency, and costs while ensuring PII is never sent in events. - Use the instance-based Posthog() constructor, enable exception autocapture, and call shutdown() to ensure all events are flushed.

### PostHog Integration for Next.js App Router - Initialize PostHog using instrumentation-client.ts and secure all API keys using environment variables. - Trigger analytics events directly within user action handlers rather than using useEffect hooks. - Identify users during authentication and maintain session correlation by passing distinct IDs via custom request headers.