signals-scout-ai-observability

Monitors PostHog LLM traces for cost, latency, error, and eval regressions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams running LLM features in PostHog need continuous oversight of cost, latency, errors, volume, and evaluation performance, but manually watching these metrics across models, products, and users is impractical and regressions go unnoticed.

Core Features & Use Cases

  • Multi-lens LLM monitoring: Watches eight observability lenses (cost, latency, errors, volume, eval performance, eval/enrichment config, clusters, tool usage) against per-team baselines learned over time.
  • Report authoring and deduplication: Authors validated regression reports directly to the PostHog inbox via emit-report/edit-report, editing existing reports instead of duplicating known issues.
  • Durable cross-run memory: Persists baselines, noise patterns, addressed incidents, and reviewer routing in a scratchpad so each run builds on prior findings.
  • Use Case: A team's LLM spend doubles after a model swap; the scout localizes the cost step to a specific model and ai_product slice, samples representative traces as evidence, and files a report routed to the owning engineer.

Quick Start

Run the AI observability scout against this PostHog project and report any validated LLM cost, latency, error, or eval regressions you find.

Frequently Asked Questions about signals-scout-ai-observability

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

FAQPage Schema
How do I monitor LLM cost and latency in PostHog?

Use the AI observability scout, which trends $ai_total_cost_usd and $ai_latency percentiles per model against learned baselines. It localizes regressions by slicing on model, provider, ai_product, and custom dimensions, then samples representative traces as evidence.

What LLM observability signals does this scout watch?

It watches eight lenses: cost, latency, errors, volume, eval performance, eval/enrichment config health, trace clusters, and tool usage. Each lens has defined signals, slicing dimensions, and disqualifiers documented in references/lenses.md.

How does the scout avoid duplicate regression reports?

It checks a report:llm_analytics scratchpad pointer and searches inbox-reports-list before authoring. If a live report already covers the slice, it appends a note with the fresh window's numbers instead of creating a new report.

Does the scout report every LLM error spike it finds?

No. It filters known noise such as provider rate limits, HITL interrupts, CI eval bursts, and scheduled batch jobs, and records benign recurring classes as noise: scratchpad entries with re-investigation tripwires.

What MCP tools and permissions does the scout require?

It requires read-only PostHog analytics scopes plus signal_scout_internal:write for the scratchpad and signal_scout_report:write for emit-report and edit-report. It uses the signals-scout MCP tool family and LLM analytics query tools.