Tutti i servizi Apigee hybrid in esecuzione nel tuo cluster Kubernetes generano informazioni sui log operativi. Queste informazioni del log sono utili per la risoluzione dei problemi e il debug. Ad esempio, se lo stato di un pod di servizio indica un problema, puoi esaminare i file di log relativi al pod per avere informazioni in merito. L'assistenza Apigee potrebbe chiederti di fornire informazioni sui log per diagnosticare e risolvere un problema.
Informazioni sul logging
Ogni servizio del piano di runtime scrive i dati dei log in stdout/stderr e Kubernetes li scrive nel file system dell'host. Un raccoltore di log per l'esecuzione ibrida su ogni nodo ibrido. Il raccoltore รจ un DaemonSet (replicato una sola volta per nodo) il cui compito รจ raccogliere i dati dei log scritti ed esportarli nell'applicazione Stackdriver Logging associata al tuo account Google Cloud.
Il seguente diagramma mostra la procedura di raccolta dei dati dei log:
[[["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 documentation version 1.1 is end of life and users should upgrade to a newer version.\u003c/p\u003e\n"],["\u003cp\u003eApigee hybrid services running in Kubernetes clusters generate operational logs that are valuable for troubleshooting and debugging purposes.\u003c/p\u003e\n"],["\u003cp\u003eEach runtime plane service logs to stdout/stderr, which Kubernetes then writes to the host filesystem, and a dedicated collector on each node then exports the logs.\u003c/p\u003e\n"],["\u003cp\u003eThe log collector, a DaemonSet, gathers log data and exports it to Stackdriver Logging in the associated GCP account.\u003c/p\u003e\n"]]],[],null,["# Logging overview\n\n| You are currently viewing version 1.1 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\nAll of the Apigee hybrid services that run in your Kubernetes\ncluster output operational log information. This log information is\nuseful for troubleshooting and debugging. For example, if a service\npod's status indicates a problem, you can look at the log files for\nthat pod to gain insight into the issue. Apigee support may request\nyou to provide log information to diagnose and solve a problem.\n\nAbout logging\n-------------\n\nEach runtime plane service writes log data to stdout/stderr, and\nKubernetes writes this data to the host filesystem. A logs\ncollector for hybrid runs on each hybrid node. The\ncollector is a [DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/) (replicated once and only once per node) whose job it\nis to collect the written log data and export it to the\n[Stackdriver Logging](https://cloud.google.com/logging/docs/)\napplication associated with your GCP account.\n\nThe following diagram shows the log data collection process:\n\nNext steps\n----------\n\n- [Enable access logs](/apigee/docs/hybrid/v1.1/access-logs)\n- [View logs](/apigee/docs/hybrid/v1.1/logging-view)"]]
