Find your next open-source project

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

monitoring-capture-service

Diagnose capture service latency, event loss, and Kafka or Redis issues using PostHog metrics and logs.

When to use it

You have a capture health symptom like rising latency or dropped events and need to find which deployment, Kafka topic, or Redis instance is behind it.

For example

You say

Use monitoring-capture-service to check prod-us capture-analytics for Kafka backpressure over the last hour and tell me which topics are lagging.

You get
  • Kafka lag summary
  • Affected topic list
  • PostHog query link

How it works

  • Asks which environment (prod-us or prod-eu) to investigate when you don't specify.
  • Discovers live metric names and labels through PostHog MCP instead of relying on fixed metric names.
  • Maps each capture deployment to its namespace, Kafka topics, and Redis instances.

Before installing

Needs a PostHog MCP connection to the internal project for the region you investigate; EU requires a separate connection to the EU PostHog instance.