Pod metrics annotations details Stay organized with collections Save and categorize content based on your preferences.
Overview
Apigee hybrid uses the industry-standard Prometheus add-on for metrics collection. All Apigee hybrid runtime plane applications expose an HTTP(s) endpoint that aPrometheus server can scrape. The Metrics are formatted inOpenCensus format.
You can use your own metrics collection and reporting service, keeping in mind that Apigee hybrid metrics are formatted in OpenCensus for scraping by a Prometheus server.
The following table lists port number and endpoint where hybrid exposes metrics for scraping for each runtime plane pods.
| Apigee component name | Port number | Metrics endpoint |
|---|---|---|
| Cassandra | 7070 | /metrics |
| Connect Agent | 7070 | /metrics |
| Mart | 8843 | /v1/mart/metrics |
| Redis | 8001 | /stats/promethues |
| Runtime | 8843 | /v1/server/metrics |
| Synchronizer | 8843 | /v1/sync/metrics |
| UDCA | 7070 | /v1/server/metrics |
| Watcher | 8843 | /metricz |
Example
The following example shows collecting metrics on the Runtime component from the command line:
kubectl -n apigee port-forwardRUNTIME_POD_NAME 8843:8843curl -k https://0:8843/v1/server/metrics?type="prometheus"
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.