Generated banner for Error Tracking Node
Generated logo for Error Tracking Node

Error Tracking Node

PostHogOfficialCreated by PostHog

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

From the author

PostHog error tracking for Node.js
— the description by PostHog

AutoGineer summary

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

This skill provides guidance on implementing PostHog error tracking within Node.js server-side environments. It covers SDK initialization, exception capture strategies, and best practices for maintaining observability in long-running or short-lived processes. The skill emphasizes using environment variables for configuration, leveraging autocapture for global exceptions, and using manual capture for specific error boundaries to ensure comprehensive monitoring.

What it does

  • Guides the installation and configuration of the posthog-node SDK.
  • Provides patterns for capturing exceptions in route handlers and middleware.
  • Explains how to optimize event flushing for different process types.
  • Details the importance of uploading source maps for readable stack traces.
  • Outlines methods for assigning issues and setting up alerts for error spikes.

When to use it

  • When you need to monitor server-side errors in a Node.js application.
  • When you want to centralize error reporting and user action tracking.
  • When you need to resolve minified stack traces using source maps.
  • When you want to automate issue assignment and alerting for your development team.

Advantages

  • Enables unified tracking of user actions and system exceptions.
  • Supports automated issue assignment based on error properties.
  • Provides flexible alerting options including Slack, Discord, and webhooks.
  • Allows for granular control over event flushing to suit various server architectures.

Usage examples

“How do I initialize PostHog in my Express app for error tracking?”
The skill instructs you to use the posthog-node SDK, enable exception autocapture in the constructor, and integrate captureException in your error middleware.
“How can I alert my team when a specific error spikes?”
The skill explains how to configure spike alerts in the PostHog error tracking settings to notify teams when error rates exceed historical baselines.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/posthog/error-tracking-node/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip error-tracking-node.zip -d .agents/skills

Documentation by PostHog

PostHog error tracking for Node.js

This skill helps you add PostHog error tracking to Node.js applications.

Reference files

  • references/node.md - Node.js error tracking installation - docs

  • references/fingerprints.md - Fingerprints - docs

  • references/alerts.md - Send error tracking alerts - docs

  • references/monitoring.md - Monitor and search issues - docs

  • references/assigning-issues.md - Assign issues to teammates - docs

  • references/upload-source-maps.md - Upload source maps - docs

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

Key principles

  • Environment variables: Always use environment variables for PostHog keys and host URLs. Never hardcode them.

  • Minimal changes: Add error tracking alongside existing error handling. Don't replace or restructure existing error handling code.

  • Autocapture first: Enable exception autocapture in the SDK initialization before adding manual captures.

  • Source maps: Upload source maps so stack traces resolve to original source code, not minified bundles.

  • Manual capture for boundaries: Use captureException() at error boundaries and catch blocks for errors that don't propagate to the global handler.

Framework guidelines

  • posthog-node is the Node.js server-side SDK package name – do NOT use posthog-js on the server

  • Include enableExceptionAutocapture: true in the PostHog constructor options

  • Add posthog.capture() calls in route handlers for meaningful user actions – every route that creates, updates, or deletes data should track an event with contextual properties

  • Add posthog.captureException(err, distinctId) in the application's error handler (e.g., Express error middleware, Fastify setErrorHandler, Koa app.on('error'))

  • In long-running servers, the SDK batches events automatically – do NOT set flushAt or flushInterval unless you have a specific reason to

  • For short-lived processes (scripts, CLIs, serverless), set flushAt to 1 and flushInterval to 0 to send events immediately

  • Reverse proxy is NOT needed for server-side Node.js – only client-side JavaScript needs a proxy to avoid ad blockers

  • Remember that source code is available in the node_modules directory

  • Check package.json for type checking or build scripts to validate changes

Files

references/node.md

Node.js error tracking installation - Docs

  1. 1

    Install the package

    Required

    Install the PostHog Node.js library using your package manager:

    PostHog AI

    npm
    npm install posthog-node
    yarn
    yarn add posthog-node
    pnpm
    pnpm add posthog-node
  2. 2

    Initialize PostHog

    Required

    Initialize the PostHog client with your project token:

    Node.js

    PostHog AI

    import { PostHog } from 'posthog-node'
    const client = new PostHog(
        '<ph_project_token>',
        {
            host: 'https://us.i.posthog.com'
        }
    )
  3. 3

    Send an event

    Recommended

    Once installed, you can manually send events to test your integration:

    Node.js

    PostHog AI

    client.capture({
        distinctId: 'distinct_id_of_the_user',
        event: 'event_name',
        properties: {
            property1: 'value',
            property2: 'value',
        },
    })
  4. 4

    Configure exception autocapture

    Recommended

    You can enable exception autocapture when initializing the PostHog client to automatically capture uncaught exceptions and unhandled rejections in your Node app.

    Node.js

    PostHog AI

    import { PostHog } from 'posthog-node'
    const client = new PostHog(
        '<ph_project_token>',
        { host: 'https://us.i.posthog.com', enableExceptionAutocapture: true }
    )

    If you are using the Express framework, you will need to import and call setupExpressErrorHandler with your PostHog client and Express app. This is because Express handles uncaught exceptions internally meaning exception autocapture will not work by default.

    server.ts

    PostHog AI

    import express from 'express'
    import { PostHog, setupExpressErrorHandler } from 'posthog-node'
    const app = express()
    const posthog = new PostHog(POSTHOG_PROJECT_TOKEN)
    setupExpressErrorHandler(posthog, app)

    Note: Error tracking requires access the file system to process stack traces. Some providers, like Cloudflare Workers, do not support Node.js runtime APIs by default and need to be included as per their documentation.

  5. 5

    Manually capture exceptions

    Optional

    If you need to manually capture exceptions, you can do so by calling the captureException method:

    Node.js

    PostHog AI

    posthog.captureException(e, 'user_distinct_id', additionalProperties)

    This is helpful if you've built your own error handling logic or want to capture exceptions normally handled by the framework.

  6. Verify error tracking

    Recommended

    Confirm events are being sent to PostHog

    Before proceeding, let's make sure exception events are being captured and sent to PostHog. You should see events appear in the activity feed.

    Image: Activity feed with eventsImage: Activity feed with events

    Check for exceptions in PostHog

  7. 6

    Upload source maps

    Required

    Great, you're capturing exceptions! If you serve minified bundles, the next step is to upload source maps to generate accurate stack traces.

    Let's continue to the next section.

    Upload source maps

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.

Needs: Needs Node.js

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/error-tracking/skills/node · 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 error-tracking-node.zip