Stay organized with collections Save and categorize content based on your preferences.
This page describes how you can understand the health of your applications and maintain application availability and reliability.
Default observability featuresBy default, GKE clusters are configured to do the following:
By default, GKE creates a Logging repository for storing logs for each cluster. You can control which logs and which metrics, if any, are sent from your GKE cluster to Cloud Logging and Cloud Monitoring.
You can also control whether to enable Google Cloud Managed Service for Prometheus.
For GKE Autopilot clusters, you cannot disable the Cloud Monitoring and Cloud Logging integration.
Additional observability metricsYou can collect additional observability metrics by enabling one or more observability metrics packages.
If you have enabled GKE Enterprise in your project, these metrics are enabled by default when you register to a fleet during cluster creation.
Third-party and user-defined metricsTo monitor third-party applications running on your clusters such as Postgres, MongoDB, and Redis, use Prometheus exporters with Google Cloud Managed Service for Prometheus.
You can also write custom exporters to monitor other signals of health and performance.
Use collected dataUse the data you collect to analyze application health, debug, troubleshoot, and test as you develop, deploy, and maintain your applications.
GKE provides built-in observability features to get you started quickly:
View collected data for your clusters and workloads on in GKE observability dashboards. You can customize the provided dashboards for the following purposes:
You can also create your own dashboards or import Grafana dashboards to meet your needs.
Note: The provided GKE dashboards only display information for GKE clusters running on Google Cloud. They don't display information for GKE clusters running anywhere else, for example using on-premises or bare-metal servers.From the Observability tab, you can create recommended alert policies so that you are notified about issues. To learn more about alerting, see the Alerting overview.
Create SLOs to monitor your service performance goals using collected GKE metrics.
Use GKE playbooks to troubleshoot common issues such as unschedulable Pods and containers that repeatedly crash after restart.
Explore and analyze your data with tools such as Logs Explorer, Metrics Explorer and Error Reporting.
Review GKE audit logs that record administrative activities and accesses as part of Cloud Audit Logs. Audit log policy determines which events are recorded and whether a log entry belongs to an Admin Activity log or a Data Access log.
GKE integrates with other Google Cloud services to help you monitor and manage your clusters and workloads.
Use the security posture dashboard to identify security concerns based on our standards and industry best practices.
View insights and recommendations to optimize your clusters.
Use network policy logging to help you troubleshoot issues with Kubernetes network policies. If you use GKE Dataplane V2, then network policy logging is built-in.
Pricing for integration with Cloud Logging (including Cloud Audit Logs), Cloud Monitoring, and Google Cloud Managed Service for Prometheus is based on the amount of logs and metrics collected. See the Pricing page for details.
Features provided by other Google Cloud services listed in Other features have separate pricing. See the Pricing section of those documentation pages for more information.
What's nextObserve your clusters. Learn how to view dashboards, organize cluster information, and view alerting details.
Enable verbose, OS-level audit logging on GKE cluster nodes and how to export logs to Cloud Logging.
For more information about how to use observability features to troubleshoot GKE, see Introduction to GKE troubleshooting.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-12 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-12 UTC."],[],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4