Apigee Hybrid utilizza il componente aggiuntivo Prometheus standard di settore per la raccolta delle metriche. Tutte le applicazioni del piano di runtime ibrido Apigee espongono un endpoint HTTP(s) che un server Prometheus puรฒ eseguire lo scraping. Le metriche sono formattate in formato
OpenCensus.
Puoi utilizzare il tuo servizio di raccolta e generazione di report sulle metriche, tenendo presente che
le metriche di Apigee hybrid sono formattate in OpenCensus per lo scraping da parte di un server Prometheus.
La tabella seguente elenca il numero di porta e l'endpoint in cui Hybrid espone le metriche per lo scraping per ogni pod del piano di runtime.
Nome del componente Apigee
Numero porta
Endpoint delle metriche
Cassandra
7070
/metrics
Agente Connect
7070
/metrics
Mart
8843
/v1/mart/metrics
Redis
8001
/stats/promethues
Runtime
8843
/v1/server/metrics
Sincronizzatore
8843
/v1/sync/metrics
UDCA
7070
/v1/server/metrics
Watcher
8843
/metricz
Esempio
L'esempio seguente mostra la raccolta delle metriche sul componente Runtime dalla riga di comando:
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema รจ stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-04 UTC."],[[["\u003cp\u003eApigee hybrid utilizes Prometheus for metrics collection, with all runtime plane applications exposing an HTTP(s) endpoint for scraping.\u003c/p\u003e\n"],["\u003cp\u003eMetrics from Apigee hybrid are formatted in OpenCensus, designed for use with a Prometheus server.\u003c/p\u003e\n"],["\u003cp\u003eEach Apigee hybrid component exposes metrics through specific port numbers and endpoints, detailed in the provided table.\u003c/p\u003e\n"],["\u003cp\u003eThe provided example shows how to collect metrics from the Runtime component using \u003ccode\u003ekubectl\u003c/code\u003e and \u003ccode\u003ecurl\u003c/code\u003e commands.\u003c/p\u003e\n"]]],[],null,["# Pod metrics annotations details\n\n| You are currently viewing version 1.14 of the Apigee hybrid documentation. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nOverview\n--------\n\n\nApigee hybrid uses the industry-standard Prometheus add-on for metrics collection. All\nApigee hybrid runtime plane applications expose an HTTP(s) endpoint that a\n[Prometheus](https://prometheus.io/)\nserver can scrape. The Metrics are formatted in\n[OpenCensus](https://opencensus.io/introduction/) format.\n\n\nYou can use your own metrics collection and reporting service, keeping in mind that\nApigee hybrid metrics are formatted in OpenCensus for scraping by a Prometheus server.\n\n\nThe following table lists port number and endpoint where hybrid exposes metrics for scraping for\neach runtime plane pods.\n\n### Example\n\n\nThe following example shows collecting metrics on the Runtime component from the command line: \n\n```\nkubectl -n APIGEE_NAMESPACE port-forward RUNTIME_POD_NAME 8843:8843\ncurl -k https://0:8843/v1/server/metrics?type=\"prometheus\"\n```"]]
