Configure OpenTelemetry log export from Next.js to PostHog via OTLP.
npx skills add https://github.com/FrekiManagarm/dunlo --skill logs-nextjs-frekimanagarm
Please help me install this Agent Skill. Skill: logs-nextjs Source: https://github.com/FrekiManagarm/dunlo/tree/main/.agents/skills/logs-nextjs Command: npx skills add https://github.com/FrekiManagarm/dunlo --skill logs-nextjs-frekimanagarm
It helps you get useful, queryable PostHog log ingestion working in Next.js by wiring OpenTelemetry Logs to PostHog’s OTLP endpoint with correct Next.js-specific setup.
Add PostHog log ingestion to your Next.js app by configuring an OpenTelemetry logger provider that exports logs to https://us.i.posthog.com/i/v1/logs using your project token from environment variables, and ensure logs are flushed in route handlers.
High-intent search queries and answers about installing and using this skill.
To send structured logs from Next.js to PostHog, you can configure an OpenTelemetry Logs provider to export events over OTLP HTTP to PostHog's ingestion endpoint using your project token. This captures backend log events for querying in PostHog.
Setting up OpenTelemetry instrumentation for Next.js 15.3 logging involves configuring the logger provider in the instrumentation-client.ts file. This ensures server-side log events are correctly captured and exported via OTLP before route handlers finish execution.
Yes, you can and should use environment variables to configure PostHog log ingestion in Next.js. This best practice involves passing your PostHog project token from environment variables into the OTLP exporter setup to keep credentials secure and manageable.
The best way to ensure Next.js API route logs are flushed to PostHog is to explicitly trigger log flushing within your route handlers. This guarantees that structured log events are exported via OTLP before the server-side request cycle completes.
Yes, PostHog log ingestion supports structured logging with trace context in Next.js. By using OpenTelemetry Logs over OTLP, you can attach structured key-value attributes and trace or session context to enable correlation in PostHog.
A limitation of using OTLP for Next.js server-side logging is ensuring reliable export behavior during serverless execution. It requires minimal code changes and careful placement of instrumentation to prevent logs from being dropped before requests terminate.
PostHogConfigure Go OTel OTLP exporter to send logs to PostHog endpoint.
PostHogConfigure OpenTelemetry OTLP log export to PostHog for non-primary languages.
EthGlobalBangkokIntegrate PostHog analytics into Next.js App Router with client and server instrumentation.
FernanSuozaImplement OpenTelemetry SDK instrumentation and collector pipelines with OTLP export.
