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

signals-scout-data-pipelines

Detects delivery failures in PostHog CDP destinations, transformations, batch exports, and hog flows.

713|118|Updated Aug 11, 2020
Search Tags:#CDP#PostHog#failure detection#Monitoring#Data pipelines#hog flows#batch exports
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill signals-scout-data-pipelines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: signals-scout-data-pipelines
Source: https://github.com/PostHog/posthog-foss/tree/main/products/signals/skills/signals-scout-data-pipelines
Command: npx skills add https://github.com/PostHog/posthog-foss --skill signals-scout-data-pipelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Data pipeline failures in PostHog are silent: events keep ingesting and dashboards stay green while destinations stop delivering, batch exports stall, and flows error for recipients. This Skill continuously audits CDP functions, batch exports, and hog flows against their own baselines to catch delivery contradictions before downstream systems quietly starve.

Core Features & Use Cases

  • Watcher intervention detection: Finds enabled functions the hog watcher degraded or auto-disabled (states 2/3) after sustained failures, which teams rarely notice.
  • Delivery failure analysis: Compares per-destination failure share against historical baselines using metrics and logs, naming the error class (HTTP 4xx/5xx, timeouts, runtime errors) and dating the onset.
  • Batch export and flow monitoring: Detects Failed export runs, stalled schedules, record-level failures, and active flows with concentrated error kinds, quantifying impact by affected recipients.
  • Use Case: A destination syncing events to Stripe starts returning HTTP 401s after a credential expires. The scout detects the failure share jumping from 0.4% to 38%, confirms the error class in logs, and files a prioritized report routed to the pipeline owner.

Quick Start

Ask the scout to check all enabled PostHog destinations, batch exports, and flows for delivery failures and report any contradictions against their baselines.

Frequently Asked Questions about signals-scout-data-pipelines

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

FAQPage Schema
How do I detect failing PostHog destinations and transformations?▼

Run a fleet-wide state scan with cdp-functions-list filtered to enabled functions, then check watcher states (2 degraded, 3 auto-disabled). For deeper analysis, retrieve per-function metrics and logs to date the failure onset and identify the error class.

How to monitor PostHog batch export failures and stalls?▼

Query system.batch_exports for live exports, then inspect the 10 latest runs per export via batch-export-get. Failed runs are terminal data gaps requiring backfill, and a newest interval lagging over 2x the export cadence indicates a stalled schedule.

What counts as a real pipeline anomaly versus normal noise?▼

A signal is a contradiction between configured state and actual delivery, such as an enabled function the watcher stopped or failure share above 10% over 24 hours. Drafts, paused exports, large filtered counts, and self-recovered blips are baseline noise, not findings.

Does this scout cover PostHog data warehouse syncs?▼

No, data warehouse and external-data syncs belong to a separate data-warehouse scout and surface as external_data_failure health issues owned by the health-checks scout. This scout covers only CDP destinations, transformations, batch exports, and hog flows.

Why does the type filter on cdp-functions-list return zero results?▼

The type filter must be a comma-separated string like "destination,transformation", not a JSON array. Passing an array silently returns zero results, which is a known footgun of the REST tools.

When should the scout edit a report instead of filing a new one?▼

Edit when a live inbox report already covers the same pipeline issue, appending fresh numbers via scout-edit-report. Author a new report only when nothing live covers it, or when the prior report was resolved and the pipeline broke again.

Related Skills

Explore More Data & Analytics Skills→
mongo-aimongo-ai

posthog-pipeline-diagnosis

Diagnose PostHog CDP pipeline and function failures blocking event delivery.

Community
Intermediate
finosfinos
14

vulnerability-resolver

Triage and resolve CVEs from Dependency-Check scan reports with suppression generation.

Official
Advanced
PostHogPostHog
58

auditing-warehouse-data-health

Audits PostHog warehouse health by surfacing active failures across sources, schemas, views, destinations, and transformations.

Official
Intermediate
abhishekmmgnabhishekmmgn

canary

Monitor live app behavior against pre-deploy baselines to detect errors and regressions.

Community
Advanced