gke-observability

Configure GKE observability with Cloud Logging, monitoring, and managed Prometheus.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/wangx7/skills-collection --skill gke-observability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gke-observability
Source: https://github.com/wangx7/skills-collection/tree/main/google-skills/skills/cloud/gke-observability
Command: npx skills add https://github.com/wangx7/skills-collection --skill gke-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GKE observability setup is complex and error-prone, with default configurations missing critical control plane metrics, leading to blind spots in cluster health, troubleshooting delays, and unplanned downtime for production workloads.

Core Features & Use Cases

  • Golden Path Observability Configuration: Provides pre-defined, production-ready defaults for Cloud Logging, Cloud Monitoring, and managed Prometheus, including critical control plane metrics for API server, scheduler, and controller manager that are not enabled by default.
  • Production Best Practices: Includes guidance for setting up actionable alerts, optimizing monitoring costs for non-production environments, and recommendations for distributed tracing and continuous profiling for microservice architectures.
  • Use Case: A DevOps engineer managing a production GKE cluster can use this skill to enable full observability, set up alerts for pod crash loops and high API server latency, and reduce monitoring costs for development clusters by switching to system-only monitoring.

Quick Start

Use the gke-observability skill to configure full observability for your GKE cluster including Cloud Logging, managed Prometheus, and control plane monitoring metrics.

Frequently Asked Questions about gke-observability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure full observability for a GKE cluster?

Configure GKE observability by enabling Cloud Logging, Cloud Monitoring, and managed Prometheus. This setup includes pre-defined production defaults and critical control plane metrics for the API server, scheduler, and controller manager to eliminate cluster health blind spots.

Why am I missing control plane metrics in Cloud Monitoring for GKE?

Missing control plane metrics in Cloud Monitoring occur because GKE default configurations omit critical API server, scheduler, and controller manager data. Applying production-ready observability configurations enables these metrics to prevent troubleshooting delays and unplanned downtime.

What is the best way to reduce Cloud Monitoring costs for non-production GKE clusters?

Reduce Cloud Monitoring costs for non-production GKE clusters by switching to system-only monitoring configurations. This optimization limits data ingestion to essential system metrics while maintaining baseline cluster health visibility.

How do I set up actionable alerts for GKE using managed Prometheus?

Set up actionable GKE alerts using managed Prometheus by applying production best practices for alert routing. Configure specific alerts for pod crash loops and high API server latency to monitor critical workload and control plane health.

Can I implement distributed tracing for microservices on GKE?

Implement distributed tracing for microservices on GKE using recommended observability configurations. This includes integrating tracing best practices alongside managed Prometheus and Cloud Logging to isolate performance bottlenecks in microservice architectures.

Does GKE observability setup support continuous profiling for microservice workloads?

GKE observability setup supports continuous profiling recommendations for microservice workloads. Configuring profiling alongside distributed tracing and managed Prometheus provides deep visibility into application performance and resource utilization.