Skill Store 33

Logs Nodejs

PostHog log ingestion for Node.js applications using OpenTelemetry and an OTLP exporter pointed at P

by posthog · MIT

The skill

PostHog log ingestion for Node.js applications using OpenTelemetry and an OTLP exporter pointed at PostHog's ingest endpoint, with keys and endpoints read from environment variables. Use when adding PostHog logs to a Node.js app, configuring log export alongside existing logging, searching logs, linking logs to session replay, or troubleshooting missing log data.

PostHog logs for Node.js

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

Reference files

  • references/nodejs.md - Node.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

No specific framework guidelines.

Use this skill

Connect your agent to the Skill Store MCP server and ask for it by ref: posthog/logs-nodejs-41819292965.

Download SKILL.md · Markdown version

Details

Publisher
posthog
Category
Software Development › DevOps & cloud
License
MIT
Updated
2026-10-19

References

More from posthog