signals-scout-error-tracking

Detects $exception bursts, stuck loops, and status regressions in PostHog error tracking.

713|118|Updated Aug 11, 2020
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill signals-scout-error-tracking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signals-scout-error-tracking
Source: https://github.com/PostHog/posthog-foss/tree/main/products/signals/skills/signals-scout-error-tracking
Command: npx skills add https://github.com/PostHog/posthog-foss --skill signals-scout-error-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams drowning in raw exception volume struggle to tell a genuine regression from background noise. This Skill watches PostHog $exception activity for meaningful changes — bursts, stuck retry loops, multi-fingerprint clusters, and resolved issues that start firing again — and files a validated, deduplicated report only when a finding clears the bar.

Core Features & Use Cases

  • Signal-vs-noise discrimination: Uses the count vs distinct_users relationship on $exception events to separate broad-reach regressions from single-user quirks and retry storms.
  • Pattern detection: Identifies fresh bursts, stuck loops, multi-fingerprint clusters with shared root causes, and status regressions on previously resolved issues.
  • Report authoring with dedupe: Authors or edits inbox reports via the report channel, using scratchpad memory keys (pattern:, noise:, dedupe:, report:) so recurring issues are edited rather than duplicated.
  • Use Case: A deploy introduces a per-request server error. The scout spots count ≈ distinct_users spiking on one fingerprint, correlates the stack-trace activity name with a recent deploy via activity logs, and files a P1 report with hourly evidence and a chart.

Quick Start

Ask the Signals agent to run the error tracking scout against your PostHog project and report any fresh $exception regressions worth acting on.

Frequently Asked Questions about signals-scout-error-tracking

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

FAQPage Schema
How do I detect error tracking regressions in PostHog?

Filter query-error-tracking-issues-list to status=active sorted by last_seen_at, then compare recent_24h_count and recent_24h_users against baseline. A spike in both count and distinct users indicates a fresh broad-reach regression worth investigating.

How to tell a real error burst from a retry loop?

Compare count against distinct_users on the $exception event. A very high count with very low distinct users indicates a stuck loop or retry storm, while count roughly equal to distinct users suggests a per-request server path affecting many users.

Does this scout duplicate reports for recurring issues?

No. It checks the inbox and scratchpad report: keys before authoring, and edits an existing live report with fresh evidence via append_note instead of filing a new one. Only a resolved issue regressing after closure earns a fresh report.

What error patterns does the scout skip?

It skips single-user single-session occurrences, sandbox-internal exceptions like Docker TimeoutExpired errors, and known upstream provider errors such as Anthropic or OpenAI rate limits, recording them as noise memory instead of reports.

Can the scout correlate errors with recent deploys?

Yes. When a server-side stack trace names a failing activity or view, the scout pairs it with advanced-activity-logs-list to find recent deploys or model changes, strengthening the report with cross-source evidence.