[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-03 (世界標準時間)。"],[],[],null,["# Application Monitoring overview\n\n| **Preview**\n|\n|\n| This product or feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products and features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nThis document introduces *Application Monitoring* , which is an application-centric\napproach to monitoring your applications. Application Monitoring provides\nout-of-the-box (OOTB) dashboards for your\n[App Hub](/app-hub/docs/overview) applications, services, and\nworkloads. To understand which resources your application uses and\nhow those resources interact, you use App Hub. To understand how\nyour application's resources are performing and to diagnose issues, you use the\ntelemetry data, which Application Monitoring displays on OOTB dashboards.\n\nWhat is Application Monitoring?\n-------------------------------\n\nApplication Monitoring lets you monitor the resources and infrastructure from the\nperspective of an application. That is, you don't begin an investigation\nby searching your resources and figuring out which ones are used by your\napplication. Instead, you begin an investigation with your application, and then\nfind information about the resources and infrastructure that it uses.\nThe OOTB dashboards generated for your\napplication let you understand the operational state of\nyour application and its services and workloads.\n\nTo use Application Monitoring, you must\n[create your application and register services and workloads to the application](/app-hub/docs/overview)\nand then configure the observability scope. To create an application and\nregister services and workloads to it, you can use App Hub,\nor you can deploy your application by using\nthe [Application Design Center](/application-design-center/docs/overview).\n\nWhy you should adopt Application Monitoring\n-------------------------------------------\n\nUsing Application Monitoring can save you time and effort. For example, suppose you\nuse the [Application Design Center](/application-design-center/docs/overview)\nto help you design and deploy your application. Next, you use\nApp Hub to help you organize and manage that application, and you use\nApplication Monitoring to understand the performance of your application and to diagnose\nfailures:\n\n- OOTB application, service, and workload dashboards\n- Label propagation for the services and workloads of an App Hub applications.\n- Filter telemetry by criticality and environment.\n- Seamless integration with open-source\n\nWhen your application is deployed, the Application Monitoring service\ndiscovers your application and automatically builds dashboards tailored\nto your environment. To support your investigation of incidents, these\nOOTB dashboards support search and filtering.\n\nThe OOTB dashboards display the following:\n\n- Information like the location, criticality, and owners.\n- Information about open incidents.\n- Log and metric data generated by [supported infrastructure](/monitoring/docs/application-monitoring-services). The metric data includes golden signals, like error rates and traffic, and select metrics.\n\nWhen your applications run on\n[supported infrastructure](/monitoring/docs/application-monitoring-services),\nGoogle Cloud Observability attaches application-specific labels to your telemetry data.\nThese labels identify your App Hub application.\nYou can use these application-specific labels when querying your telemetry\ndata. The **Logs Explorer** , **Metrics Explorer** , and\n**Trace Explorer** pages let you use labels to filter and aggregate\ndata.\n\nGet started with Application Monitoring\n---------------------------------------\n\nTo use Application Monitoring, do the following:\n\n1. Configure the observability scope so that you can view the telemetry for an\n application that is registered with\n [App Hub](/app-hub/docs/overview). For information\n about this step, see\n [Set up Application Monitoring](/monitoring/docs/setup-application-monitoring).\n\n2. Attach application-specific labels to your alerting policies.\n For information about this step, see\n [Associate an alerting policy with an App Hub application](/monitoring/docs/setup-application-monitoring#alert).\n\n3. If you want your application-generated metric and trace data to include\n application labels, then instrument your application with OpenTelemetry or use\n Google Cloud Managed Service for Prometheus. For more information, see\n [Instrument app for Application Monitoring](/monitoring/docs/instrument-for-application-monitoring).\n\n | **Note:** For workloads that run on Google Kubernetes Engine, the OOTB dashboards display OpenTelemetry-defined metrics for traffic, latency, and error rate golden signals.\n4. Open and explore the OOTB dashboards. For information about viewing\n these dashboards, see [View application telemetry](/monitoring/docs/application-monitoring)."]]