Google Cloud Managed Service for Prometheus를 사용해서 구성된 타사 및 사용자 정의 측정항목을 수집하고 이를 Cloud Monitoring에 전송합니다. Google Cloud Managed Service for Prometheus를 사용하면, 대규모 Prometheus를 수동으로 관리 및 운영할 필요 없이 Prometheus를 사용하여 워크로드를 모니터링하고 알림을 보낼 수 있습니다.
데이터 수집 맞춤설정 및 강화
기본적으로 GKE는 각 클러스터의 로그를 저장하는 Logging 저장소를 만듭니다. GKE 클러스터에서 Cloud Logging 및 Cloud Monitoring으로 전송되는 로그 및 측정항목을 제어할 수 있습니다.
네트워크 정책 로깅을 사용하면 Kubernetes 네트워크 정책 관련 문제를 해결하는 데 도움이 됩니다. GKE Dataplane V2를 사용하는 경우 네트워크 정책 로깅이 기본 제공됩니다.
가격 책정
Cloud Logging(Cloud 감사 로그 포함), Cloud Monitoring, Google Cloud Managed Service for Prometheus와 통합에 대한 가격 책정은 수집되는 로그 및 측정항목의 양에 따라 달라집니다. 자세한 내용은 가격 책정 페이지를 참조하세요.
기타 기능에 나열된 다른 Google Cloud 서비스에서 제공되는 기능에는 각기 다른 가격 책정이 적용됩니다. 자세한 내용은 해당 문서 페이지의 가격 책정 섹션을 참조하세요.
다음 단계
클러스터를 관찰합니다.
대시보드를 보고, 클러스터 정보를 구성하고, 알림 세부정보를 확인하는 방법을 알아보세요.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2024-11-25(UTC)"],[],[],null,["[Autopilot](/kubernetes-engine/docs/concepts/autopilot-overview) [Standard](/kubernetes-engine/docs/concepts/choose-cluster-mode)\n\n*** ** * ** ***\n\nThis page describes how you can understand the health of your applications and\nmaintain application availability and reliability.\n\nDefault observability features\n\nBy default, GKE clusters are configured to do the following:\n\n- Send [system logs, audit logs, and application logs](/kubernetes-engine/docs/concepts/about-logs#what_logs) to Cloud Logging.\n- Send [system metrics](/kubernetes-engine/docs/how-to/configure-metrics#system-metrics) to Cloud Monitoring.\n- Use [Google Cloud Managed Service for Prometheus](/stackdriver/docs/managed-prometheus) to collect configured third-party and user-defined metrics and then send them to Cloud Monitoring. Google Cloud Managed Service for Prometheus lets you monitor and alert on your workloads using Prometheus, without manually managing and operating Prometheus at scale.\n\nCustomize and enhance data collection\n\nBy default, GKE creates a Logging repository for\nstoring logs for each cluster. You can control which logs and which metrics, if\nany, are sent from your GKE cluster to Cloud Logging and\nCloud Monitoring.\n\nYou can also control whether to enable\n[Google Cloud Managed Service for Prometheus](/stackdriver/docs/managed-prometheus).\n\nFor GKE Autopilot clusters, you cannot disable\nthe Cloud Monitoring and Cloud Logging integration.\n\nAdditional observability metrics\n\nYou can collect additional observability metrics by enabling one or more\n[observability metrics packages](/kubernetes-engine/docs/how-to/configure-metrics).\n\n- [Control plane metrics](/kubernetes-engine/docs/how-to/control-plane-metrics): Monitor the health of Kubernetes components by collecting metrics for the Kubernetes API server, Scheduler, and Controller Manager. These metrics are useful signals of service health for defining service level objectives (SLOs).\n- [Kube state metrics](/kubernetes-engine/docs/how-to/kube-state-metrics): Monitor the health of Kubernetes objects such as Deployments, Nodes, and Pods.\n- [cAdvisor/Kubelet metrics](/kubernetes-engine/docs/how-to/cadvisor-kubelet-metrics): Monitor the health of containers and the kubelet.\n\nThird-party and user-defined metrics\n\nTo monitor third-party applications running on your clusters such as Postgres,\nMongoDB, and Redis, use\n[Prometheus exporters](/stackdriver/docs/managed-prometheus/exporters/introduction)\nwith Google Cloud Managed Service for Prometheus.\n\nYou can also\n[write custom exporters](https://prometheus.io/docs/instrumenting/writing_exporters/)\nto monitor other signals of health and performance.\n\nUse collected data\n\nUse the data you collect to analyze application health, debug, troubleshoot,\nand test as you develop, deploy, and maintain your applications.\n\nGKE provides built-in observability features to get you started\nquickly:\n\n- View collected data for your clusters and workloads on in\n GKE\n [observability dashboards](/kubernetes-engine/docs/how-to/view-observability-metrics).\n You can customize the provided dashboards for the following purposes:\n\n - View key cluster metrics, such as CPU utilization, memory utilization, and the number of open incidents.\n - View clusters by their infrastructure, workloads, or Services.\n - Inspect namespaces, Nodes, workloads, Services, Pods, and containers.\n - For Pods and containers, view metrics as a function of time and view log entries.\n\n You can also [create your own dashboards](/monitoring/charts/dashboards) or\n [import Grafana dashboards](/monitoring/dashboards/import-grafana-dashboards)\n to meet your needs.\n | **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.\n- From the **Observability** tab, you can create recommended alert policies so\n that you are notified about issues. To learn more about alerting, see the\n [Alerting overview](/monitoring/alerts).\n\n- [Create SLOs](/stackdriver/docs/solutions/slo-monitoring/ui/create-slo) to\n monitor your service performance goals using collected GKE\n metrics.\n\n- Use GKE playbooks to troubleshoot common issues such as\n [unschedulable Pods](/kubernetes-engine/docs/troubleshooting/deployed-workloads#PodUnschedulable)\n and\n [containers that repeatedly crash after restart](/kubernetes-engine/docs/troubleshooting/deployed-workloads#CrashLoopBackOff).\n\n- Explore and analyze your data with tools such as\n [Logs Explorer](/logging/docs/view/logs-explorer-interface),\n [Metrics Explorer](/monitoring/charts/metrics-explorer) and\n [Error Reporting](/error-reporting/docs/grouping-errors).\n\n- Review GKE\n [audit logs](/kubernetes-engine/docs/how-to/audit-logging) that record\n administrative activities and accesses as part of\n [Cloud Audit Logs](/logging/docs/audit).\n [Audit log policy](/kubernetes-engine/docs/concepts/audit-policy) determines\n which events are recorded and whether a log entry belongs to an Admin Activity\n log or a Data Access log.\n\nOther features\n\nGKE integrates with other Google Cloud services to help you\nmonitor and manage your clusters and workloads.\n\n- Use the\n [security posture dashboard](/kubernetes-engine/docs/concepts/about-security-posture-dashboard)\n to identify security concerns based on our standards and industry best\n practices.\n\n- View\n [insights and recommendations](/kubernetes-engine/docs/how-to/optimize-with-recommenders)\n to optimize your clusters.\n\n- Use\n [network policy logging](/kubernetes-engine/docs/how-to/network-policy-logging)\n to help you troubleshoot issues with Kubernetes network policies. If you use\n [GKE Dataplane V2](/kubernetes-engine/docs/concepts/dataplane-v2), then\n network policy logging is built-in.\n\nPricing\n\nPricing for integration with Cloud Logging (including\nCloud Audit Logs), Cloud Monitoring, and Google Cloud Managed Service for Prometheus is\nbased on the amount of logs and metrics collected. See the\n[Pricing](/stackdriver/pricing) page for details.\n\nFeatures provided by other Google Cloud services listed in\n[Other features](#other-features) have separate pricing. See the Pricing section\nof those documentation pages for more information.\n\nWhat's next\n\n- [Observe your clusters](/kubernetes-engine/docs/how-to/view-observability-metrics).\n Learn how to view dashboards, organize cluster information, and view alerting\n details.\n\n- [Enable verbose, OS-level audit logging](/kubernetes-engine/docs/how-to/linux-auditd-logging)\n on GKE cluster nodes and how to export logs to\n Cloud Logging.\n\n- For more information about how to use observability features to troubleshoot\n GKE, see\n [Introduction to GKE troubleshooting](/kubernetes-engine/docs/troubleshooting/introduction)."]]
