[[["容易理解","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-04 (世界標準時間)。"],[],[],null,["# Learn more about...\n\n| **Beta**\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\nAggregation\n-----------\n\nWhen you read metric data using the Metrics Explorer or the Monitoring API,\nyou can use *aggregation* to summarize the time series data. Aggregation\ntypically starts with an alignment step in which each time series' data is\nplaced on the same time boundaries. Next, a new time series is created by\ncombining the data points from multiple time series, using operations like\naverage, sum, minimum, maximum, and so forth.\n\nFor more information about aggregation, see the\n[`projects.timeSeries.list`](/monitoring/api/ref_v3/rest/v3/projects.timeSeries/list)\nAPI method.\n\nCustom metrics\n--------------\n\nCloud Monitoring has a large number of built-in system metrics, but you can\nalso create custom metrics. You must create a metric descriptor that\ndescribes your custom metric and one or more time series that contain its data.\nYou can use your custom metric data in charts and alerts. You can also create\ncustom metrics based on logs data. For more information, see the following\npages:\n\n- [Metrics, Time Series, and Resources](/monitoring/api/v3/metrics) provides an overview.\n- [Using Custom Metrics](/monitoring/custom-metrics) shows you how to create, write, and read custom metrics.\n- [Logs-based Metrics](/logging/docs/view/logs_based_metrics) describes how to create custom metrics from logs.\n- [Monitoring API](/monitoring/api/ref_v3/rest), is the API used to for custom metrics. See the `projects.metricDescriptors` and `projects.timeSeries` collections.\n\nFiltering\n---------\n\nCloud Logging and Cloud Monitoring provide different kinds of filters\nthat let you select\nsets of items. Filters are strings that contain combinations of comparisons\nappropriate to their kind. For example:\n\n- [Logging filters](/logging/docs/view/advanced_filters) let you select particular log entries based on log names, where the logs came from, their payload content, and so on.\n- [Monitoring filters](/monitoring/api/v3/filters) let you select particular metric descriptors, resource groups, and time series data.\n- [Trace filters](/trace/docs/trace-filters) let you select traces based on span names, latency, and label values.\n\nMetrics scope\n-------------\n\nMonitoring organizes itself around metrics scopes that\nlet you view and monitor metrics for one or more Google Cloud projects.\nFor more information about metrics scopes, see\n[Configuring your Google Cloud project for Cloud Monitoring](/monitoring/settings)."]]
