Agent skill · data analytics · jeremylongshore
posthog-observability
Observe a PostHog integration through application-side delivery metrics, ingestion warnings, billing volume, destination logs, and status evidence. Use when defining health signals or investigating silent analytics loss. Trigger with "monitor PostHog", "PostHog ingestion health", or "PostHog alerts".
Why this skill is useful
Adds specific monitoring scripts and API queries for PostHog integration health that are not commonly known.
What it needs
Requires jq installed locally. Requires posthog account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
PostHog Observability Overview Observe four boundaries independently: application capture attempts and failures, SDK queue and flush behavior, PostHog ingestion warnings and accepted event volume, and feature-flag cache or remote-fallback behavior. Treat every Prometheus metric below as application-owned instrumentation, not as a metric exported by PostHog. Prerequisites PostHog project with personal API key (phx...) Application instrumented with PostHog SDK Prometheus/Grafana or equivalent monitoring stack (optional) Instructions Tool discipline Use Read to inspect the relevant configuration and implementation before proposing changes. Use Write only for a new, explicitly requested artifact inside the target project. Use Edit for minimal changes to existing project files after the evidence pass. Step 1: Event Ingestion Health Check Step 2: Instrument Flag Evaluation Latency Step 3: Monitor Event Volume and Billing Step 4: Prometheus Alert Rules Step 5: Health Check Dashboard Queries Error Handling Issue Cause Solution ------- ------- ---------- Zero events for 1h+ SDK not initialized or API down Check PostHog status, verify SDK init Flag evaluation exceeds the service SLO Cold cache, fallback, or network path Inspect secure-key configuration, cache state, and fallback counts Event volume spike New feature autocapturing Review autocapture config, add filters Rate limit 429 Too many API queries Cache results, reduce poll frequency Output Flag evaluation latency instrumentation Event volume and billing monitoring Prometheus rules over application-emitted integration metrics HogQL dashboard queries for key metrics Automated alerts for ingestion drops and billing limits Examples For a server event pipeline, instrument queue depth, flush failures, request latency, and fallback counts in the application; correlate them with ingestion warnings and billing volume. Do not claim PostHog exposes Prometheus metrics unless the target deployment proves that surface. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/posthog-observability