Overview of Google Cloud's operations suite for GKE

Google Kubernetes Engine (GKE) includes native integration with Cloud Monitoring and Cloud Logging. When you create a GKE cluster, Kubernetes Engine Operations is enabled by default and provides a monitoring dashboard specifically tailored for Kubernetes.

With Kubernetes Engine Operations, you can control whether or not Cloud Logging collects application logs. You also have the option to disable the Cloud Monitoring and Cloud Logging integration altogether. For more information on the installation instructions, see Installing Monitoring and Logging support for GKE.

About Kubernetes Engine Operations

Kubernetes Engine Operations is designed to monitor GKE clusters. It manages Monitoring and Logging services together and features a Kubernetes Engine Operations dashboard that provides a customized interface for GKE clusters:

  • In the summary pane, you can view a cluster's key metrics, such as CPU utilization, memory utilization, and the number of open incidents.

  • You can view clusters by their infrastructure, workloads, or services.

  • You can inspect namespaces, nodes, workloads, services, pods, and containers.

  • For pods and containers, you can view metrics as a function of time and view log entries using the Logs Viewer.

Which monitoring and logging option should I use?

You can use the default Kubernetes Engine Operations dashboard or opt-in to use Legacy Logging and Monitoring. Both options are generally available as of GKE version 1.12.7. Here are some issues to consider:

  • Kubernetes Engine Operations is the default option, starting with GKE version 1.14.

  • Legacy Logging and Monitoring is also a generally available option; however, it lacks features and improvements present in Kubernetes Engine Operations.

  • Only Legacy Logging and Monitoring lets you disable Cloud Logging while still using Cloud Monitoring.

Selecting your Google Cloud's operations suite support for GKE

If you are using Legacy Logging and Monitoring, then you must switch to Kubernetes Engine Operations before support for Legacy Logging and Monitoring is removed. Legacy Logging and Monitoring will no longer be supported as of GKE 1.15. The table below details compatibility across GKE versions:

GKE version Legacy Logging and Monitoring Kubernetes Engine Operations
1.10 – 1.12.5 Default Opt-in (Beta)
1.12.7 Default Optional
1.13 Default Optional
1.14 Optional Default
1.15 Not Available Default


Kubernetes Engine Operations is priced based on the amount of logs and metrics collected. See the Pricing page for details.

Kubernetes Engine Operations how-to guides

  • Installing Kubernetes Engine Operations: Describes how to enable Kubernetes Engine Operations in new and existing clusters.

  • Migrating to Kubernetes Engine Operations: Describes the differences between Legacy Logging and Monitoring and Kubernetes Engine Operations and what you must change in your Google Cloud's operations suite configurations as part of updating your monitoring and logging integration.

  • Observing your system: Describes the Kubernetes Engine Operations dashboard interface, how to organize cluster information, and how to view alerting details.

  • Enabling auditd logs: Describes how to enable verbose, OS-level audit logging on GKE cluster nodes and how to export logs to Cloud Logging.

  • Using Prometheus: Optional. Describes how to configure Kubernetes Engine Operations for Prometheus.

Legacy Logging and Monitoring how-to guides

  • Legacy Cloud Monitoring: Describes how to set up the legacy solution of Cloud Monitoring for your GKE clusters.

  • Legacy Cloud Logging: Describes how to set up the legacy solution of Cloud Logging for your GKE clusters.