[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-21。"],[[["\u003cp\u003eApigee hybrid metrics can be viewed in Cloud Operations dashboards after enabling metrics collection, and the metrics have a domain name prefix of \u003ccode\u003eapigee.googleapis.com/\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eCloud Operations allows filtering and grouping of metrics data based on predefined and hybrid-added labels, with details of available metrics and their specific labels found in the "Available metrics" section.\u003c/p\u003e\n"],["\u003cp\u003eTo view Apigee hybrid metrics, use the Monitoring Metrics Explorer in Cloud Operations to locate, select, and filter the desired metrics, then save the chart for display.\u003c/p\u003e\n"],["\u003cp\u003eCustom dashboards can be created in Cloud Operations to analyze metric data, where charts displaying Apigee metrics can be added and configured as needed, providing control over what data is visualized.\u003c/p\u003e\n"],["\u003cp\u003eCritical Cassandra metrics, including request rate and latency for reads and writes, along with pod CPU and data volume utilization, should be monitored to assess cluster health and determine when scaling may be needed, which can be based on a set of parameters and metrics described in the article.\u003c/p\u003e\n"]]],[],null,["# View metrics\n\n| You are currently viewing version 1.12 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nThis topic explains how to view Apigee hybrid metrics in a\n[Cloud Operations](/monitoring/kubernetes-engine) dashboard.\n\nAbout Cloud Operations\n----------------------\n\nFor more information about metrics, dashboards, and [Cloud Operations](/monitoring/kubernetes-engine) see:\n\n- [Metrics Explorer documentation](https://cloud.google.com/monitoring/charts/metrics-explorer)\n- [Introduction to alerting](/monitoring/alerts)\n- [Creating charts](/monitoring/charts)\n\nEnabling hybrid metrics\n-----------------------\n\nBefore hybrid metrics can be sent to\n[Cloud Operations](/monitoring/kubernetes-engine),\nyou must first enable metrics collection. See [Configure metrics collection](/apigee/docs/hybrid/v1.12/metrics-enable)\nfor this procedure.\n| **Note:** Metrics for the Apigee ingress gateway is not supported. See [Known issues](/apigee/docs/release/known-issues).\n\nAbout hybrid metric names and labels\n------------------------------------\n\nWhen enabled, hybrid automatically populates Cloud Operations metrics. The domain name prefix\nof the metrics created by hybrid is: \n\n```text\napigee.googleapis.com/\n```\n\nFor example, the `/proxy/request_count` metric contains the total number of requests received\nby an API proxy. The metric name in Cloud Operations is therefore: \n\n```scdoc\napigee.googleapis.com/proxy/request_count\n```\n\nCloud Operations lets you [filter](/monitoring/charts/metrics-selector#filter-option)\nand [group](/monitoring/charts/metrics-selector#groupby-option)\nmetrics data based on labels. Some labels are predefined, and others are added explicitly by hybrid.\nThe [Available metrics](#available_metrics) section below lists all of the available hybrid\nmetrics and any labels added specifically for a metric that you can use for filtering and grouping.\n\nViewing metrics\n---------------\n\nThe following example shows how to view metrics in Cloud Operations:\n\n1. Open the [Monitoring Metrics Explorer](https://console.cloud.google.com/monitoring/metrics-explorer) in a browser. Alternatively, if you're already in the Cloud Operations console, select **Metrics explorer**.\n2. In **Find resource type and metric** , locate and select the\n metric you want to examine. Choose a specific metric listed in\n [Available metrics](#available_metrics), or search for a metric.\n\n3. Select the desired metric.\n4. Apply filters. Filter choices for each metric are listed in [Available metrics](#available-metrics).\n5. Cloud Operations displays the chart for the selected metric.\n6. Click **Save**.\n\nCreating a dashboard\n--------------------\n\n[Dashboards](/monitoring/dashboards)\nare one way for you to view and analyze metric data that is important to you.\nCloud Operations provides predefined dashboards for the resources and services that you use,\nand you can also create custom dashboards.\n\nYou use a [chart](/monitoring/dashboards)\nto display an Apigee metric in your custom dashboard. With custom dashboards, you have complete control\nover the charts that are displayed and their configuration. For more information on creating charts, see\n[Creating charts](/monitoring/charts).\n\nThe following example shows how to create a dashboard in Cloud Operations and then to add charts to view metrics data:\n\n1. Open the [Monitoring Metrics Explorer](https://console.cloud.google.com/monitoring/metrics-explorer) in a browser and then select **Dashboards**.\n2. Select **+ Create Dashboard**.\n3. Give the dashboard a name. For example: **Hybrid Proxy Request Traffic**\n4. Click **Confirm**.\n5. For each chart that you want to add to your dashboard, follow these steps:\n\n 1. In the dashboard, select **Add chart**.\n 2. Select the desired metric as described above in [Viewing metrics](#view_metrics).\n 3. Complete the dialog to define your chart.\n 4. Click **Save**. Cloud Operations displays data for the selected metric.\n\nAvailable metrics\n-----------------\n\nThe following tables list metrics for analyzing proxy traffic. For more information about each Apigee metric,\nsee [Google cloud metrics](/monitoring/api/metrics_gcp#gcp-apigee).\n\n### Proxy, target, and server traffic metrics\n\nOpen Telemetry collects and processes metrics (as described in [Metrics collection](/apigee/docs/hybrid/v1.12/metrics-collection)) for\nproxy, target, and server traffic.\n\nThe following table describes the metrics that the Open Telemetry collector uses.\n\n### UDCA metrics\n\nOpen Telemetry collects and processes metrics (as described in [Metrics collection](/apigee/docs/hybrid/v1.12/metrics-collection)) for the\nUDCA service just as it does for other hybrid services.\n\nThe following table describes the metrics that the Open Telemetry collector uses in the\nUDCA metrics data.\n\n### Cassandra metrics\n\nOpen Telemetry collects\nand processes metrics (as described in [Metrics collection](/apigee/docs/hybrid/v1.12/metrics-collection)) for\nCassandra just as it does for other hybrid services.\n\nThe following table describes the metrics that the Open Telemetry collector uses in the\nCassandra metrics data.\n\n#### Working with Cassandra metrics\n\n\nApigee recommends the following metrics as critical to monitor for your Cassandra database:\n\n- **Cassandra request rate** : Use this metric to monitor the cassandra read and write request rate.\n\n\n To monitor cassandra read request rate, apply the following filter.\n\n\n To monitor cassandra write request rate, apply the following filter.\n\n- **Cassandra request latency** : Use this metric to monitor the cassandra read and write request latency. This is the same metric as the request rate, `apigee.googleapis.com/cassandra/clientrequest_latency` with different filters applied.\n\n\n To monitor cassandra read request latency, apply the following filter.\n\n\n To monitor cassandra write request latency, apply the following filter.\n\n- **Cassandra pod CPU request utilization** **Note:** Cassandra pod CPU request metrics are only available in GKE.\n\n- **Cassandra data volume utilization** **Note:** Cassandra data volume utilization metrics are only available in GKE.\n\n#### Recommendations for scaling the Cassandra cluster\n\n\nThe following guidelines can serve as a recommended cluster for the decision to scale your\nCassandra cluster. In general, if read or write requests consistently show 99th percentile latency\nor the latency is trending upwards continuously, and you see corresponding spikes in CPU request\nutilization spike and the read or write request rates, your Cassandra cluster can be considered\nto be under stress. You may want to consider scaling up the cluster. For more information see\n[Scaling Cassandra](/apigee/docs/hybrid/v1.12/cassandra-scaling)"]]
