Google Cloud Monitoring vs Pixie

Google Cloud Monitoring provides visibility into the performance, availability, and health of applications and infrastructure. It automatically collects metrics for Google Cloud services and also supports hybrid and multicloud environments. The service brings together metrics, uptime checks, dashboards, and alerts; users can build custom dashboards and multi-condition alert policies. Service-level objectives can be inferred automatically or defined by users, with alerts for violations. Script-based synthetic monitors test web applications and APIs. For Kubernetes, Managed Service for Prometheus handles managed or self-deployed metric collection. On supported Linux and Windows virtual machines, the Ops Agent collects logs and metrics and includes third-party application integrations. Alerts can be sent through email, Slack, PagerDuty, Pub/Sub, SMS, webhooks, or the Cloud Mobile App. Cloud Monitoring API v3 offers programmatic access to metrics scopes, dashboards, and alerting policies. It runs in the cloud and lists API, Linux, web, and Windows platforms. Pricing is usage-based, with free monthly allotments on several meters; charges can depend on ingested data, time series returned, and check executions.

Pixie is open-source Kubernetes observability and debugging software for developers. It collects metrics, events, traces, and logs without code changes, using dynamic eBPF probes and ingestors. Users can run community, team, or custom scripts to debug as code and share sessions. Its CLI provides health checks and charts, with a browser interface available when needed. Pixie supports hosted and self-hosted deployments; its Vizier data-collection component runs in the Kubernetes cluster. Requirements include Kubernetes v1.21 or later and Linux nodes, and pods that install BPF programs need privileged access to the Linux kernel. The project lists Cosmic Cloud and New Relic Cloud as free hosted versions. Pixie lists Minikube, EKS, GKE, AKS, and self-managed Kubernetes environments. Telemetry traffic is encrypted in transit. The requirements page says telemetry passes through Pixie Cloud without persistence, while the install guide says hosted-backend telemetry data is stored exclusively on the Kubernetes cluster, not in Pixie Cloud. Listed unsupported environments include EKS Fargate, GKE Autopilot, Docker Desktop, k3d, kind, and Windows. Help options include Community Slack, a troubleshooting guide, and GitHub issues.