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://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/debug-logs-mcp.md

Debug Logs with MCP - Docs

The PostHog MCP server gives AI agents direct access to your Logs. Ask your agent to search, filter, and analyze log data without leaving your code editor.

With MCP, your agents can:

  • Search and filter logs – Query by severity level, service name, date range, and free text.

  • Discover log attributes – List available attributes and their values to build targeted queries.

  • Debug in context – Investigate production issues without switching tools.

  • Correlate with traces – Use trace IDs and span IDs from log entries to follow request flows across services.

This works in any MCP client – Cursor, Windsurf, Claude Code, and others.

Example prompts

Try these prompts with your MCP-enabled agent:

  • Show me all error logs from the last hour.

  • What services are logging errors? Search for error logs from the payments service.

  • Find logs related to trace ID abc123.

  • What log attributes are available? Show me the values for the service.name attribute.

  • Show me warning and error logs from the last 24 hours, excluding debug noise.

Logs tools

The MCP server provides three tools for working with logs:

ToolDescription
logs-querySearch and query logs with filters for severity levels (trace, debug, info, warn, error, fatal), service names, date ranges, and free text. Supports pagination for large result sets.
logs-list-attributesList available log attributes in your project to discover what you can filter on. Supports filtering by attribute type (log or resource).
logs-list-attribute-valuesGet possible values for a specific log attribute. Find service names, log levels, or other attribute values before querying.

A typical workflow:

  1. Call logs-list-attributes to discover available filter attributes.

  2. Call logs-list-attribute-values to find specific values (e.g., which service names exist).

  3. Call logs-query to search logs with the right filters.

Get started

See the MCP server documentation for setup instructions.

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 or PostHog.

Download ZIP

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