skills.rest
PostHog
PostHogOFFICIAL
Explore all skills by this author →
Website𝕏@PostHogGitHub

grouping-noisy-errors

Merge duplicate PostHog error tracking issues and create grouping rules for future events.

713|118|Updated Aug 11, 2020
Search Tags:#deduplication#error tracking#PostHog#fingerprint#exception monitoring#merge issues#grouping rules
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill grouping-noisy-errors
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grouping-noisy-errors
Source: https://github.com/PostHog/posthog-foss/tree/main/products/error_tracking/skills/grouping-noisy-errors
Command: npx skills add https://github.com/PostHog/posthog-foss --skill grouping-noisy-errors

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The same error can appear as dozens of separate PostHog error tracking issues when stack frames or messages contain volatile data like random IDs, build hashes, or dynamic file paths. This Skill consolidates those duplicate fingerprints into one canonical issue and prevents future events from spawning new ones.

Core Features & Use Cases

  • Duplicate Detection: Compares candidate issues by SDK, exception type, top stack frame, message template, and handled status to confirm they are truly the same error before merging.
  • One-Shot Merge: Collapses existing duplicate issues into a chosen target issue using the PostHog error tracking merge API, with batching guidance for large sprawl.
  • Durable Grouping Rules: Creates ingestion-time grouping rules that rewrite matching event fingerprints to a single canonical value, with safe filter construction on $exception_types, $exception_sources, and $exception_values.
  • Use Case: A team sees 40 separate TypeError issues that all originate from the same checkout bundle file with hashed filenames. Use this Skill to verify they share a stack frame, merge them into the highest-occurrence issue, and add a grouping rule so future events route to one issue.

Quick Start

Ask the assistant to find and merge the duplicate TypeError issues in PostHog error tracking and set up a grouping rule so they stop splitting into new issues.

Frequently Asked Questions about grouping-noisy-errors

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I merge duplicate error issues in PostHog?▼

Use the error-tracking-issues-merge-create tool with a target issue ID and a list of duplicate IDs. First confirm the duplicates share the same SDK, exception type, top stack frame, and message template, then merge in batches of about 50 IDs.

What is the difference between merging issues and grouping rules in PostHog?▼

Merging is a one-shot operation that collapses existing issues into a target. A grouping rule is durable and rewrites matching event fingerprints at ingestion time so future events share one canonical fingerprint instead of creating new issues.

Why does my PostHog grouping rule never match any events?▼

The most common cause is filtering on the wrong $lib value, since the browser SDK captures $lib as web rather than posthog-js. Also avoid filtering on singular properties like $exception_type, which appear on only a fraction of events.

When should I not group errors that look similar?▼

Do not group errors across different SDKs, runtimes, files, or top stack functions, even if the exception type and message match. Also keep caught and uncaught variants separate, since they represent different code paths.

Can I undo a merge in PostHog error tracking?▼

Merges are destructive and source issues disappear from the active list. Use error-tracking-issues-split-create to surgically separate fingerprints back out of a merged issue if the merge was a mistake.

Related Skills

Explore More Software Engineering Skills→
FrekiManagarmFrekiManagarm

error-tracking-web

Integrate PostHog error tracking into JavaScript web applications.

Community
Intermediate
jlawsjlaws
2

github-issue-resolution

Triage GitHub issues and generate pull requests with root-cause analysis.

Community
Advanced
UnicornUnicorn

alerting-rules-agent

Generate Prometheus alert rules and PagerDuty routing configurations.

Official
Intermediate
telum-aitelum-ai
2

sentry-integration

Integrate Sentry error tracking and performance monitoring in React/Next.js applications.

Official
Intermediate