PostHog logs for Node.js
SkillMonitoring & opsPostHog logs for Node.js
Available today. Use it from your connected AI after setup.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the PostHog logs for Node.js skill
What this skill tells your AI
The instructions your AI receives, as published by posthog/skills in skills/posthog/all/skills/logs-nodejs/SKILL.md and read by ahel’s review.
This skill helps you add PostHog log ingestion to Node.js applications.
Reference files
references/nodejs.md- Node.js logs installation - docsreferences/start-here.md- Getting started with logs - docsreferences/search.md- Search logs - docsreferences/best-practices.md- Logging best practices - docsreferences/troubleshooting.md- Logs troubleshooting - docsreferences/link-session-replay.md- Link session replay - docsreferences/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.
Signals
- GitHub stars
- 71
- Forks
- 7
- Last commit
- Sep 2026
ahel review
K1binfo
installs-packages (in references/nodejs.md)
Automated review, not a security audit. Ruleset v1+k2.
Advanced
- Item type
- skill
- Key
logs-nodejs- Source
- github.com/posthog/skills