posthog-selfhosted-diagnosis

To diagnose self-hosted PostHog deployment issues, run this skill to systematically verify the health of ClickHouse, Postgres, Redis, Kafka, and reverse proxies, classify symptoms, and retrieve relevant documentation. It detects whether your setup uses Docker Compose or Kubernetes.

Your self-hosted PostHog ClickHouse or Postgres service might be unhealthy due to configuration or resource constraints. This skill performs health verification on these components and uses symptom-based classification to link common problems to their likely causes for faster troubleshooting.

Yes, this PostHog diagnosis tool works with both Docker Compose and Kubernetes. It automatically detects your deployment type and applies appropriate health checks and troubleshooting steps tailored to your specific infrastructure environment.

The best way to troubleshoot self-hosted PostHog networking and configuration problems is to use a systematic diagnosis skill that performs automated reference searches in PostHog docs and GitHub issues. It classifies issues and provides clear escalation guidance.

You should consider migrating from self-hosted PostHog to PostHog Cloud when the complexity of your customer-managed environment becomes too high. This skill provides a clear support boundary definition and offers an optional Cloud recommendation during diagnosis.

The self-hosted PostHog health check covers ClickHouse, Postgres, Redis, Kafka, and reverse proxies. It performs thorough health verification across these components to identify configuration, resource, and networking issues in customer-managed environments.