[[["์ดํดํ๊ธฐ ์ฌ์","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-12-13(UTC)"],[],[],null,["# Logging and monitoring\n\nThis section describes how logging and monitoring work in the enterprise\napplication blueprint for both the developer platform and the applications.\n[Google Cloud Observability for GKE](/stackdriver/docs/solutions/gke)\nprovides Cloud Logging and Cloud Monitoring services for blueprint\napplications.\n\nBy\ndefault, the base source code in the application templates sends logs to\n`stdout`. Using `stdout` is a best practice for containerized applications\nbecause `stdout` lets the platform handle the application logs. The application\ncode is instrumented with Prometheus client libraries to [export application-specific metrics](/stackdriver/docs/managed-prometheus/setup-managed#gmp-pod-monitoring).\nGKE automatically provides metrics for each application,\nincluding [Kube State metrics](/stackdriver/docs/managed-prometheus/exporters/kube_state_metrics),\nresource utilization, [SRE golden metrics](/stackdriver/docs/solutions/gke/app-performance-metrics#app-perf-ingest),\nand database instance metrics. For the developer platform team, the platform\nprovides infrastructure, usage, and cross-application traffic metrics.\n\nLogging storage\n---------------\n\nCloud Operations for GKE also lets you collect system and\napplication logs into [central log buckets](/logging/docs/storage). The blueprint also\nincludes a project in each environment folder that's used for storing logs. The enterprise foundation\nblueprint has a separate [logging project](/architecture/blueprints/security-foundations/detective-controls#centralized-logging)\nwhere the aggregate Cloud Audit Logs logs from across the entire\nGoogle Cloud organization are exported. The log types most needed by\ntenants are also separated by tenant. For example, an application developer who\nworks on the `frontend` application might be granted access to only `frontend`\ncontainer logs and pod logs, and only in the development and non-production\nenvironments.\n\nThe following table lists log types, locations, and access control granularity.\n\nApplication monitoring\n----------------------\n\nGoogle Cloud Observability for GKE provides [predefined monitoring dashboards](/monitoring/dashboards) for\nGKE. The blueprint also enables [Google Cloud Managed Service for Prometheus](/stackdriver/docs/managed-prometheus), which\ncollects metrics from Prometheus exporters and lets you query the data globally\nusing PromQL. PromQL means that you can use familiar tools like Grafana\ndashboards and PromQL-based alerts. Cloud Service Mesh is enabled to provide\nyou with\n[dashboards](/service-mesh/docs/observability-overview)\nin the Google Cloud console to observe and troubleshoot interactions between\nservices and across tenants. The blueprint also includes a project for a\n[multi-project monitoring metrics scope](/monitoring/settings).\n\nThreat and vulnerability monitoring\n-----------------------------------\n\n[Security Command Center](/security-command-center/docs/security-command-center-overview)\nprovides insight into the overall security posture of the blueprint.\nSecurity Command Center Premium tier provides\n[Container Threat Detection](/security-command-center/docs/concepts-container-threat-detection-overview)\nfor active container-based workloads in GKE.\n[Web Security Scanner](/security-command-center/docs/concepts-web-security-scanner-overview)\nis used to detect vulnerabilities in your internet-facing services.\nWeb Security Scanner detects vulnerabilities by crawling an HTTP service and\nfollowing all links, starting at the base URL. Web Security Scanner then exercises\nas many user inputs and event handlers as possible.\n\nWhat's next\n-----------\n\n- Read about [operations for both the developer platform and applications](/architecture/blueprints/enterprise-application-blueprint/ops-developer-platform-applications) (next document in this series)."]]
