AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

instrument-error-tracking

Add PostHog error tracking to capture and monitor exceptions. Use after implementing features or reviewing PRs to ensure errors are tracked with stack traces and source maps. Also handles initial PostHog SDK setup if not yet installed.

Original source
posthog
License
MIT
Pinned revision
cac7c80a9e5b73484d18eda1bffb47297c938e0c

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read posthog--instrument-error-tracking at revision cac7c80a9e5b73484d18eda1bffb47297c938e0c, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 30

references/nuxt-3-7.md

AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

Nuxt Error Tracking installation (v3.7 and above)

Canonical URL: https://posthog.com/docs/error-tracking/installation/nuxt-3-7

Cloud region: This page uses US Cloud hosts. For an EU Cloud project, use https://eu.posthog.com instead of https://app.posthog.com (app host for links).

On this page

Install with the wizard

Run this command in your project directory to add PostHog to your Nuxt project. The wizard detects your framework, installs the SDK, and sets up your first events.

npx @posthog/wizard

Or set it up manually by following the rest of this guide.

  1. 1

    Install the PostHog Nuxt module

    Required

    Install the PostHog Nuxt module using your package manager:

    npm

    npm install @posthog/nuxt
    

    yarn

    yarn add @posthog/nuxt
    

    pnpm

    pnpm add @posthog/nuxt
    

    bun

    bun add @posthog/nuxt
    

    Add the module to your nuxt.config.ts file:

    nuxt.config.ts

    export default defineNuxtConfig({
      modules: ['@posthog/nuxt'],
      // Enable source maps generation in both vue and nitro
      sourcemap: {
        client: 'hidden'
      },
      nitro: {
        rollupConfig: {
          output: {
            sourcemapExcludeSources: false,
          },
        },
      },
      posthogConfig: {
        publicKey: '<ph_project_token>', // Find it in project settings https://app.posthog.com/settings/project
        host: 'https://us.i.posthog.com', // Optional: defaults to https://us.i.posthog.com. Use https://eu.i.posthog.com for EU region
        clientConfig: {
          capture_exceptions: true, // Enables automatic exception capture on the client side (Vue)
        },
        serverConfig: {
          enableExceptionAutocapture: true, // Enables automatic exception capture on the server side (Nitro)
        },
        sourcemaps: {
          enabled: true,
          projectId: '<ph_project_id>', // Your project ID, found in your environment settings: https://app.posthog.com/settings/environment#variables
          personalApiKey: '<ph_personal_api_key>', // Your personal API key from PostHog settings https://app.posthog.com/settings/user-api-keys (requires organization:read and error_tracking:write scopes)
          releaseName: 'my-application', // Optional: defaults to git repository name
          releaseVersion: '1.0.0', // Optional: defaults to current git commit
        },
      },
    })
    

    Personal API key

    Your personal API key will require organization:read and error_tracking:write scopes.

    The module will automatically:

    • Initialize PostHog on both Vue (client side) and Nitro (server side)
    • Capture exceptions on both client and server
    • Generate and upload source maps during build
  2. 2

    Manually capturing exceptions

    Optional

    Our module if set up as shown above already captures both client and server side exceptions automatically.

    To send errors manually on the client side, import it and use the captureException method like this:

    Vue

    <script>
      const { $posthog } = useNuxtApp()
      if ($posthog) {
        const posthog = $posthog()
        posthog.captureException(new Error("Important error message"))
      }
    </script>
    

    On the server side instantiate PostHog using:

    server/api/example.js

    const runtimeConfig = useRuntimeConfig()
    const posthog = new PostHog(
      runtimeConfig.public.posthogPublicKey,
      {
        host: runtimeConfig.public.posthogHost,
      }
    );
    try {
      const results = await DB.query.users.findMany()
      return results
    } catch (error) {
      posthog.captureException(error)
    }
    
  3. 3

    Build your project for production

    Required

    Build your project for production by running the following command:

    Terminal

    nuxt build
    

    The PostHog module will automatically generate and upload source maps to PostHog during the build process.

  4. 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.

    Activity feed with events

    Check for exceptions in PostHog

  5. 4

    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