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://mp-staging.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/assigning-issues.md

Assign issues to teammates - Docs

Error tracking enables you to assign issues to specific PostHog roles or teammates. This helps your team find relevant issues through filtering. You can also set up team-specific alerting to notify them when assigned issues are created or reopened.

Assign issues

You can manually assign issues as you triage them in the UI. This can be done both in the issue list and issue detail pages.

Image: Error tracking assignment UIImage: Error tracking assignment UI

  1. In your error tracking issue list, click the unassigned selector under each issue to assign it to a role or user.

  2. On the detail page of each issue, click the Assignee selector to assign it to a role or user.

Want to assign issues to a team rather than an individual teammate? You can create a role in your project settings.

Image: Error tracking role assigneesImage: Error tracking role assignees

Automatic issue assignment

You can set up automatic issue assignment through a set of rules. This can be configured in the error tracking settings using auto assignment rules.

Image: Error tracking auto assignment rulesImage: Error tracking auto assignment rules

Assignment conditions are evaluated against the properties of the exception event that created the issue. Because assignment rules are evaluated during ingestion, the stack trace (if present) will be unminified, which enables filtering on exception properties such as function name and source file.

Issues can be automatically assigned to a role or user by configuring a set of filters. These filters can be configured to match any or all of the criteria.

You can configure automatic assignment to filter on any event property in PostHog. When there are multiple values for a property, the filters return true if it matches any of the values. For example, if you have multiple exception_functions values, the filters returns true if it matches any of the functions.

Here are some common properties you can filter on:

PropertyEvent propertyDescription
Exception type$exception_typesThe type of exception(s) that occurred
Exception message$exception_valuesThe message(s) detected on the error
Exception function$exception_functionsThe function(s) where the exception occurred
Exception source$exception_sourcesThe source file(s) where the exception occurred
Exception was handled$exception_handledWhether the exception was handled by the application
Device type$device_typeThe type of device that the error occurred on
Browser$browserThe browser that the error occurred in
Current URL$current_urlThe URL that the error occurred on
Feature flag$feature_flagThe feature flag that the error occurred on

You can also set custom properties on the error tracking event to filter on. For example, setting a custom params_received property to provide more context or debug information.

Order of issue assignment rules

Issue assignment filters are evaluated in the order they are configured. They can also be reordered once created. The first filter that matches is used to assign the issue. This means you should configure the most specific filters first, and then the more general filters later.

Disabled assignment rules

Assignment rules can become disabled if an error occurs during ingestion. When a rule is disabled, a banner displays the original error message. To re-enable the rule, edit it to fix the problem and save your changes. If the issue persists, reach out to support.

Alerting based on assignment

A common use case for automatic issue assignment is to alert assignees of new issues. Once the issues are automatically assigned, you can set up alerts to notify the assignee. See the alerts guide for more information.

Create external issues

You can also create issues in external tracking systems like GitHub Issues, Linear, GitLab, or Jira.

First, set up an integration with your tracking system. Then, from an issue's details page, under External references, click Create issue.

Image: Error tracking create issue in external tracking systemImage: Error tracking create issue in external tracking system

The new issue will have a partial stack trace and a link to the issue in PostHog.

If you use another issue tracking system and would like to request it, let us know in-app.

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.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download error-tracking-ruby.zip