AutoGineer
Generated banner for Logs Nextjs
Generated logo for Logs Nextjs

Logs Nextjs

PostHogOfficialCreated by PostHog

  • Skill
  • Tool integration
  • Data and AI
  • MIT
  • No issues found
Download ZIP

From the author

PostHog logs for Next.js
— the description by PostHog

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides guidance and best practices for configuring log ingestion in Next.js applications to send data to PostHog. It emphasizes the use of the OpenTelemetry protocol and structured logging to ensure logs are actionable, searchable, and context-rich. By following these patterns, developers can centralize system logs alongside product analytics and session replays, enabling more efficient debugging and monitoring of production environments.

What it does

  • Provides instructions for setting up PostHog log ingestion in Next.js.
  • Promotes the use of structured logging over plain text for better queryability.
  • Encourages the use of wide events to capture request-level context.
  • Outlines best practices for log levels, cardinality, and business context.
  • Supports integration with OpenTelemetry for standardized data export.

When to use it

  • When you need to centralize system logs from a Next.js application.
  • When you want to correlate system logs with user sessions and product analytics.
  • When you are implementing or refactoring logging to improve production observability.
  • When you need to debug complex request flows using trace and session context.

Advantages

  • Enables unified visibility across logs, analytics, and session replays.
  • Reduces noise by focusing on request-level wide events.
  • Standardizes log data using OpenTelemetry protocols.
  • Improves debugging efficiency by linking logs to specific user sessions.

Usage examples

“How do I set up PostHog logs in my Next.js 15 application?”
The agent provides the steps to initialize PostHog in instrumentation-client.ts and configure the OTLP exporter.
“What is the best way to log payment processing in my app?”
The agent advises against step-by-step code logging, suggesting a single wide event containing relevant metadata like order_id and amount_cents.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/posthog/logs-nextjs/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip logs-nextjs.zip -d .agents/skills

Documentation by PostHog

PostHog logs for Next.js

This skill helps you add PostHog log ingestion to Next.js applications.

Reference files

  • references/nextjs.md - Next.js logs installation - docs

  • references/start-here.md - Getting started with logs - docs

  • references/search.md - Search logs - docs

  • references/best-practices.md - Logging best practices - docs

  • references/troubleshooting.md - Logs troubleshooting - docs

  • references/link-session-replay.md - Link session replay - docs

  • references/debug-logs-mcp.md - Debug logs with mcp - docs

Consult the documentation for API details and framework-specific patterns.

Key principles

  • Environment variables: Always use environment variables for PostHog keys and OpenTelemetry endpoints. Never hardcode them.

  • Minimal changes: Add log export alongside existing logging. Don't replace or restructure existing logging code.

  • OpenTelemetry: PostHog logs use the OpenTelemetry protocol. Configure an OTLP exporter pointed at PostHog's ingest endpoint.

  • Structured logging: Prefer structured log formats with key-value properties over plain text messages.

Framework guidelines

  • For Next.js 15.3+, initialize PostHog in instrumentation-client.ts for the simplest setup

Files

references/start-here.md

Getting started with logs - Docs

New to logging? Read Why you need logs first for a primer on what logs show you that nothing else does.

Install and configure logging

PostHog logs is a powerful logging solution that works with the OpenTelemetry Protocol (OTLP). You don't need any vendor specific SDKs – just use standard OpenTelemetry libraries.

Install and configure your logging client to send logs to PostHog:

  • Use the HTTP endpoint: https://us.i.posthog.com/i/v1/logs

  • Authenticate with your project token (the same token used for events/exceptions)

  • Include the token in the Authorization header or as a ?token= query parameter

  • Use the standard OTLP log format

Configure your logging client

Search and analyze your logs

Once your logs are flowing into PostHog, you can:

  • Search through logs using multiple search tokens, negative filters, and exact phrase matching

  • Filter by time ranges to find specific events

  • Correlate logs with events from your PostHog analytics

Navigate to the Logs section in your PostHog dashboard to start exploring your log data.

Learn how to search logs

Troubleshooting

Common issues you might encounter when setting up logging:

  • Authentication errors - Make sure you're using your correct project token

  • Connection issues - Verify the HTTP endpoint is accessible

  • Log format problems - Ensure you're using the standard OTLP log format

Troubleshoot common issues

Logging best practices

Learn what to log, how to structure your logs, and the patterns that make logs actually useful in production – including wide events, strategic sampling, and adding business context.

Read the best practices guide

1/4

Install and configure logging RequiredSearch and analyze your logs RequiredTroubleshooting RecommendedLogging best practices Recommended

Install and configure logging

Required

Community questions

Ask a question

Was this page useful?

HelpfulCould be better

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
PostHog
Publisher
PostHog (Official)
Source
PostHog/skills · skills/posthog/logs/skills/nextjs · commit a5d30e7
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Also distributed in
PostHog/skills

AutoGineer is not affiliated with or endorsed by PostHog.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download logs-nextjs.zip