View metrics
This topic explains how to view Apigee hybrid metrics in aCloud Operations dashboard.
About Cloud Operations
For more information about metrics, dashboards, andCloud Operations see:
Enabling hybrid metrics
Before hybrid metrics can be sent toCloud Operations,you must first enable metrics collection. SeeConfigure metrics collectionfor this procedure.
Note:Metrics for the Apigee ingress gateway is not supported. SeeKnown issues.About hybrid metric names and labels
When enabled, hybrid automatically populates Cloud Operations metrics. The domain name prefixof the metrics created by hybrid is:
apigee.googleapis.com/
For example, the/proxy/request_count metric contains the total number of requests receivedby an API proxy. The metric name in Cloud Operations is therefore:
apigee.googleapis.com/proxy/request_count
Cloud Operations lets youfilterandgroupmetrics data based on labels. Some labels are predefined, and others are added explicitly by hybrid.TheAvailable metrics section below lists all of the available hybridmetrics and any labels added specifically for a metric that you can use for filtering and grouping.
Viewing metrics
The following example shows how to view metrics in Cloud Operations:- Open theMonitoring Metrics Explorer in a browser. Alternatively, if you're already in the Cloud Operations console, selectMetrics explorer.
InFind resource type and metric, locate and select the metric you want to examine. Choose a specific metric listed inAvailable metrics, or search for a metric.
- Select the desired metric.
- Apply filters. Filter choices for each metric are listed inAvailable metrics.
- Cloud Operations displays the chart for the selected metric.
- ClickSave.
Creating a dashboard
Dashboardsare one way for you to view and analyze metric data that is important to you.Cloud Operations provides predefined dashboards for the resources and services that you use,and you can also create custom dashboards.
You use achartto display an Apigee metric in your custom dashboard. With custom dashboards, you have complete controlover the charts that are displayed and their configuration. For more information on creating charts, seeCreating charts.
The following example shows how to create a dashboard in Cloud Operations and then to add charts to view metrics data:
- Open theMonitoring Metrics Explorer in a browser and then selectDashboards.
- Select+ Create Dashboard.
- Give the dashboard a name. For example:Hybrid Proxy Request Traffic
- ClickConfirm.
For each chart that you want to add to your dashboard, follow these steps:
- In the dashboard, selectAdd chart.
- Select the desired metric as described above inViewing metrics.
- Complete the dialog to define your chart.
- ClickSave. Cloud Operations displays data for the selected metric.
Available metrics
The following tables list metrics for analyzing proxy traffic. For more information about each Apigee metric, seeGoogle cloud metrics.
Proxy, target, and server traffic metrics
Open Telemetry collects and processes metrics (as described inMetrics collection) forproxy, target, and server traffic.
The following table describes the metrics that the Open Telemetry collector uses.
| Metric name | Use |
|---|---|
/proxy/request_count | Number of requests to the Apigee proxy since the last sample was recorded.Note: Available for Apigee hybrid v1.12 and higher. |
/proxy/response_count | Number of responses sent by the Apigee API proxy.Note: Available for Apigee hybrid v1.12 and higher. |
/proxy/latencies | Distribution of latencies, which are calculated from the time the request was received by the Apigee proxy to the time the response was sent from the Apigee proxy to the client.Note: Available for Apigee hybrid v1.12 and higher. |
/proxyv2/request_count | The total number of API proxy requests received. |
/proxyv2/response_count | The total number of API proxy responses received. |
/proxyv2/latencies_percentile | Percentile of all API policy responses to a request. |
/target/request_count | Number of requests sent to the Apigee target since the last sample was recorded.Note: Available for Apigee hybrid v1.12 and higher. |
/target/response_count | Number of responses received from the Apigee target since the last sample was recorded.Note: Available for Apigee hybrid v1.12 and higher. |
/target/latencies | Distribution of latencies, which are calculated from the time the request was sent to the Apigee target to the time the response was received by the Apigee proxy. Time does not include the Apigee API proxy overhead.Note: Available for Apigee hybrid v1.12 and higher. |
/targetv2/request_count | The total number of requests sent to the proxy's target. |
/targetv2/response_count | The total number of responses received from the proxy's target. |
/server/fault_count | The total number of faults for the server application. For example, the application could be |
/server/nio | This is a gauge metric that can be filtered by the labelstate to retrieve details for various labels. The values represent different system and I/O operations. Labels such asaccepted,accepted_total,close_failed,close_success,conn_pending,connected,connected_total,max_conn, andtimeouts are related to socket and connection operations. The remaining labels pertain to other system operations. |
/server/num_threads | The number of active non-daemon threads in the server. |
/server/request_count | The total number of requests received by the server application. For example, the application could be |
/server/response_count | Total number of responses sent by the server application. For example, the application could be |
/server/latencies | Latency is the latency in millisecs introduced by the server application. For example, the application could be |
/upstream/request_count | The number of requests sent by the server application to its upstream application. For example, for the |
/upstream/response_count | The number of responses received by the server application from its upstream application. For example, for the |
/upstream/latencies | The latency incurred at the upstream server application in milliseconds. For example, for the |
Cassandra metrics
Open Telemetry collectsand processes metrics (as described inMetrics collection) forCassandra just as it does for other hybrid services.
The following table describes the metrics that the Open Telemetry collector uses in theCassandra metrics data.
| Metric name (excluding domain) | Use |
|---|---|
/cassandra/process_max_fds | Maximum number of open file descriptors. |
/cassandra/process_open_fds | Open file descriptors. |
/cassandra/jvm_memory_pool_bytes_max | JVM maximum memory usage for the pool. |
/cassandra/jvm_memory_pool_bytes_init | JVM initial memory usage for the pool. |
/cassandra/jvm_memory_bytes_max | JVM heap maximum memory usage. |
/cassandra/process_cpu_seconds_total | User and system CPU time spent in seconds. |
/cassandra/jvm_memory_bytes_used | JVM heap memory usage. |
/cassandra/compaction_pendingtasks | Outstanding compactions for Cassandra sstables. SeeCompaction for more. |
/cassandra/jvm_memory_bytes_init | JVM heap initial memory usage. |
/cassandra/jvm_memory_pool_bytes_used | JVM pool memory usage. |
/cassandra/jvm_memory_pool_bytes_committed | JVM pool committed memory usage. |
/cassandra/clientrequest_latency | Read request latency in the 75th percentile range in microseconds. |
/cassandra/jvm_memory_bytes_committed | JVM heap committed memory usage. |
Working with Cassandra metrics
Apigee recommends the following metrics as critical to monitor for your Cassandra database:
- Cassandra request rate: Use this metric to monitor the cassandra read and write request rate.
Metric: apigee.googleapis.com/cassandra/clientrequest_latencyResource labels: project_id,location,cluster_name,namespace_name,pod_name,container_nameMetric labels: scope,unitUse these labels to filter the specific resource or for grouping.
To monitor cassandra read request rate, apply the following filter.
Filters: metric.scope == 'Read'metric.unit == 'OneMinuteRate'To monitor cassandra write request rate, apply the following filter.
Filters: metric.scope == 'Write'metric.unit == 'OneMinuteRate' - 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_latencywith different filters applied.To monitor cassandra read request latency, apply the following filter.
Filters: metric.scope == 'Read'metric.unit == '99thPercentile'or'95thPercentile'or'75thPercentile'To monitor cassandra write request latency, apply the following filter.
Filters: metric.scope == 'Write'metric.unit == '99thPercentile'or'95thPercentile'or'75thPercentile' - Cassandra pod CPU request utilizationNote: Cassandra pod CPU request metrics are only available in GKE.
Metric: kubernetes.io/container/cpu/request_utilization (GKE on Google Cloud)For more information, seeKubernetes metrics.
kubernetes.io/anthos/container/cpu/request_utilization (Google Distributed Cloud)Resource labels: project_id,location,cluster_name,namespace_name,pod_name,container_nameUse these labels to filter the specific resource or for grouping.
- Cassandra data volume utilizationNote: Cassandra data volume utilization metrics are only available in GKE.
Metric: kubernetes.io/pod/volume/utilization (GKE on Google Cloud)For more information, seeKubernetes metrics.
kubernetes.io/anthos/pod/volume/utilization (Google Distributed Cloud)Resource labels: project_id,location,cluster_name,namespace_name,pod_nameMetric labels: volume_nameUse these labels to filter the specific resource or for grouping.
Recommendations for scaling the Cassandra cluster
The following guidelines can serve as a recommended cluster for the decision to scale your Cassandra cluster. In general, if read or write requests consistently show 99th percentile latency or the latency is trending upwards continuously, and you see corresponding spikes in CPU request utilization spike and the read or write request rates, your Cassandra cluster can be considered to be under stress. You may want to consider scaling up the cluster. For more information seeScaling Cassandra
| Metric | Threshold | Trigger duration |
|---|---|---|
kubernetes.io/pod/volume/utilization | 85% | 5min |
kubernetes.io/container/cpu/request_utilization | 85% | 3min |
Read request Latency 99thPercentile | 5s | 3min |
Write request Latency 99thPercentile | 5s | 3min |
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-18 UTC.