AutoGineer
Generated banner for Error Tracking Ruby
Generated logo for Error Tracking Ruby

Error Tracking Ruby

PostHogOfficialCreated by PostHog

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

From the author

PostHog error tracking for Ruby
— the description by PostHog

AutoGineer summary

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

This skill provides guidance on integrating the PostHog Ruby SDK to capture and track application exceptions. It covers initialization, manual error capturing, and best practices for managing error data, including environment variable usage and proper SDK lifecycle management in scripts and CLI tools.

What it does

  • Provides instructions for installing and initializing the posthog-ruby gem
  • Explains how to capture exceptions manually using capture_exception
  • Defines best practices for environment variable usage and SDK shutdown
  • Outlines how to integrate error tracking with existing Ruby error handling
  • Details how to manage and assign issues within the PostHog platform

When to use it

  • When you need to monitor Ruby application health and track runtime exceptions
  • When implementing error boundaries in Ruby scripts or CLI applications
  • When you want to centralize error reporting and team-based issue assignment
  • When you need to resolve stack traces using source maps

Advantages

  • Enables proactive monitoring through automated exception capture
  • Supports team collaboration via issue assignment and alerting
  • Maintains clean code by integrating with existing error handling patterns
  • Provides detailed context for debugging through stack trace resolution

Usage examples

“How do I initialize the PostHog client in a Ruby script?”
You should use PostHog::Client.new(api_key: ENV['POSTHOG_KEY'], host: ENV['POSTHOG_HOST']) and ensure you call client.shutdown in an ensure block.
“How do I manually capture an exception in Ruby?”
Use the client.capture_exception(exception, distinct_id, additional_properties) method, ensuring you pass arguments positionally.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/posthog/error-tracking-ruby/download

  2. Unzip it into the cross-client skills folder of your project:

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

Documentation by PostHog

PostHog error tracking for Ruby

This skill helps you add PostHog error tracking to Ruby applications.

Reference files

  • references/ruby.md - Ruby 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-ruby is the Ruby SDK gem name (add gem 'posthog-ruby' to Gemfile) but require it with require 'posthog' (NOT require 'posthog-ruby')

  • Use PostHog::Client.new(api_key: key, host: host) for instance-based initialization in scripts and CLIs

  • In CLIs and scripts: MUST call client.shutdown before exit or all events are lost

  • Use begin/rescue/ensure with shutdown in the ensure block for proper cleanup

  • capture and identify take a single hash argument: client.capture(distinct_id: 'user_123', event: 'my_event', properties: { key: 'value' })

  • capture_exception takes POSITIONAL args (not keyword): client.capture_exception(exception, distinct_id, additional_properties) — do NOT use distinct_id: keyword syntax

Files

references/fingerprints.md

Fingerprints - Docs

Every captured exception is assigned a fingerprint. This fingerprint is used to group similar exceptions into issues. This page covers how fingerprints are generated, how they're used, and how you can override them when capturing exceptions.

Fingerprint and issue grouping

Every exception has a fingerprint, whether generated or defined by the user. Each fingerprint links to exactly one issue. Exceptions that share the same fingerprint define an issue.

Multiple different fingerprints can point to the same issue (a many-to-one relationship) if you merge issues.

How are fingerprints generated?

Fingerprints are built iteratively using components of the exception event. The flowchart below shows how fingerprints are generated.

flowchart LR A[Add exception type to fingerprint] --> B{Stack trace<br/>available?} B -->|No| C[Add error message to fingerprint] C --> D[Final fingerprint] B -->|Yes| E{In-app frames<br/>exist?} E -->|No| F[Add first frame to fingerprint] E -->|Yes| G[Add in-app frame to fingerprint<br/>Priority: resolved > unresolved] F --> D G --> D

The flowchart in text

Fingerprints are generated by considering the following in combination:

  1. The exception type

  2. If there's no resolved stack trace, add the error message to the fingerprint

  3. If there are stack traces but no in-app frames (frames from your code, not a dependency), use the first frame of the stack trace

  4. If there are stack traces, in-app frames, and source maps available, use the resolved in-app stack frames

  5. If there are stack traces, in-app frames, and source maps not available, use the first in-app stack frame

In some languages, like Python, one error can trigger another, creating a chain of linked exceptions. PostHog records the entire chain in the event and generates a single fingerprint for it.

Ensuring accurate fingerprints

Resolved stack traces are critical for accurate fingerprinting. Without accurate stack traces, PostHog cannot group exceptions consistently. If you have not uploaded source maps, follow the source map guide to do so.

This also means that if the exception type or message changes from one version to the next, the fingerprint will change.

When are generated fingerprints used?

Fingerprints are used to group similar exceptions into issues automatically. Automatic issue grouping is only done when:

You can find details about how issue grouping works in the issues and exceptions guide.

Customizing fingerprints

Fingerprints can be manually set during exception capture. This is a very useful way to group exceptions that are not related to each other. You can find examples of how to do this in the custom issue grouping section.

You can also learn more about grouping issues using rules in the grouping issues guide.

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 an API key

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