Find your next open-source project

Search by name, purpose, or keyword — or paste a GitHub repository URL
All skills

monitoring-ingestion-pipeline

Diagnose PostHog ingestion worker lag, errors, and Kafka/Redis/ClickHouse health using PostHog MCP metrics and logs.

When to use it

You're seeing event lag or drops in production and need to trace which ingestion deployment, consumer group, or downstream service is responsible.

For example

You say

Use monitoring-ingestion-pipeline to investigate rising event lag in prod-eu. Check the analytics main and overflow lanes and tell me whether the bottleneck is Kafka consumer lag, Redis, or ClickHouse.

You get
  • Lag diagnosis by lane
  • Consumer group health check
  • Downstream bottleneck call

How it works

  • Asks which environment (prod-us or prod-eu) to investigate when unspecified.
  • Discovers live metric names via PostHog MCP instead of relying on fixed metric lists.
  • Maps deployments to pipelines, lanes, and consumer groups to narrow the failing worker.

Before installing

Requires a PostHog MCP connection to the region's internal project; prod-us and prod-eu use separate connections.