Investigating Logs
by PostHog469d1773e9cbNo licenseListed Oct 8, 2026Updated Oct 8, 2026
Investigate logs in a PostHog project: verify a service or deployment is healthy, explain an error spike, triage an incident, or understand what a log stream is saying. Use when the user asks to "check the logs", asks whether a service, deploy, release, or change is working or broke anything, asks why errors are up or what changed, or wants the root cause of failures visible in logs. Routes the logs MCP tools (services overview, pattern mining, before/after pattern diffing, bucketed counts, facets, raw rows) so investigations start from summaries instead of raw rows or hand-written SQL over the logs table.
- 469d1773e9cbCurrentcommit 469d177Published Oct 8, 2026
Source and attribution
Source:PostHog/ai-plugininskills/investigating-logsat commit469d177
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from PostHog/ai-plugin
Writing Simplified Technical English
PostHog
Applies ASD-STE100 simplified technical English rules to make agent-written prose unambiguous and actionable.
Working With Task Comments
PostHog
Reads and interprets comments on PostHog tasks, artifacts, and canvases through the PostHog MCP exec dispatcher.
Working With Skills
PostHog
Guides agents in using PostHog's skill-* MCP tools to discover, read, create, update, and refactor skills.
Working With Scouts
PostHog
Operating manual for delegating watching jobs to PostHog Signals scouts, acting on their reports, and steering the fleet over time.
Validating And Publishing Canvases
PostHog
Validate and publish a canvas source project safely: the source-project shape, declared capabilities, reading the current version pointer, iterating on validation diagnostics, guarded publishing with expected_current_version_id, staging a draft build and promoting it, waiting out the queued build, and recovering from a 409 version_conflict or a 429 capacity limit without overwriting concurrent work. Use whenever a canvas edit is ready to save, a draft build is wanted, a canvas publish or build returns diagnostics or a conflict, or a task needs to understand canvas version history.
Understanding Billing Usage
PostHog
Explains PostHog billing usage and spend from the customer's visible Billing MCP tools. Use when the user asks why usage or spend is high, which product or project is driving usage, what a usage type means, how to reduce usage, what changed over time, why they got a usage change alert, or whether a spike/drop alert was real or noisy. Also use before product-specific analytics skills when the user names a billable PostHog product metric such as events, recordings, feature flag requests, exceptions, survey responses, synced rows, logs, AI events, AI credits, or Inbox credits. Starts from Billing usage/spend tools, then routes to customer-visible product MCP surfaces for deeper investigation.
More in DevOps & Cloud
M5 Onboard
anthropics
Provisions M5Stack ESP32 boards by detecting them on USB, flashing UIFlow 2.0 firmware, and installing a MicroPython app bundle.
Spanner Basics
Guides Google Cloud Spanner administration, schema design, querying and performance diagnosis.
Secops Cases
Manages Google Security Operations SOAR cases across their lifecycle via MCP tools.
Managed Airflow Migrations
Guides migration of Apache Airflow DAGs to Airflow 2.11.1 or Airflow 3 in Managed Service for Apache Airflow.
Managed Airflow Dag Troubleshooting
Guides deterministic troubleshooting of failed Managed Service for Apache Airflow DAG runs and task instances using gcloud commands.
Iam Helper For Privileged Access Management
Guides Google Cloud Privileged Access Manager entitlement CRUD, temporary access requests, and grant approval workflows.