analytics▌

### 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 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 Ruby Integration - Install the posthog-ruby gem and initialize the client using environment variables for API keys and host configuration. - Use client.capture and client.identify with hash arguments, but use positional arguments for client.capture_exception. - Ensure client.shutdown is called before script exit to prevent event loss, ideally within an ensure block for proper cleanup.

### 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 Integration for Nuxt 3.6 - Follow the four-step setup workflow to initialize PostHog analytics within your Nuxt 3.0 to 3.6 application. - Use environment variables for all PostHog keys and maintain consistency by following the provided example project patterns. - Identify users during authentication events and use specific headers to correlate client-side sessions with backend requests.

### 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 FastAPI Integration - Initialize the Posthog client within the FastAPI lifespan context manager and ensure proper shutdown to flush all pending events. - Use dependency injection for settings and user identification, ensuring PII is only sent via identify calls, never in capture events. - Follow the provided example project patterns and use environment variables for API keys to maintain secure and consistent tracking.

### PostHog Node.js Error Tracking - Initialize the SDK with enableExceptionAutocapture set to true and use environment variables for all sensitive configuration keys. - Implement captureException in global error handlers and specific catch blocks to ensure comprehensive visibility into application failures. - Upload source maps to resolve stack traces and configure flush settings to match the lifecycle of your server or serverless process.

### PostHog Log Ingestion for Other Languages - Configure OTLP exporters to send logs directly to PostHog's ingestion endpoint using the OpenTelemetry protocol. - Use environment variables for all sensitive configuration, including PostHog project keys and OTLP endpoints. - Implement structured logging with key-value pairs to enhance searchability without replacing existing application logging logic.

### omnibus-instrument-integration Overview - >- - Use this skill to add the PostHog SDK to an application. Use it when setting up PostHog for the first time, or reviewing PRs that need PostH - Supported frameworks: Next.js, React, React Router, Vue, Nuxt, TanStack Start, SvelteKit, Astro, Angular, Django, Flask, FastAPI, Laravel, R