Generazione di log quando l'inoltro del proxy HTTP è abilitato
Quando attivi l'inoltro del proxy HTTP, crei un unico punto tramite il quale più macchine inviano richieste a un server esterno. Per la registrazione, potresti non voler inoltrare tutto il traffico tramite il proxy.
Questa procedura spiega come disattivare il reindirizzamento del proxy HTTP per host specifici nel file delle sostituzioni.
Procedura
Disattiva il proxy per la registrazione per host specifici impostando la proprietà logger.EnvVars in overrides.yaml:
La proprietà logger.EnvVars ti consente di passare le variabili di ambiente supportate da Fluent Bit. Consulta
NO_PROXY
nella documentazione di Fluent Bit.
Applica le modifiche al logger con apigeectl apply con l'ambito --telemetry:
apigeectl apply --telemetry -f overrides.yaml
Vedi anche
logger.EnvVars nel riferimento alle proprietà di configurazione.
[[["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-03 UTC."],[[["\u003cp\u003eThis document details how to disable HTTP proxy forwarding for specific hosts when logging in Apigee hybrid version 1.9.\u003c/p\u003e\n"],["\u003cp\u003eDisable proxy forwarding by setting the \u003ccode\u003elogger.EnvVars\u003c/code\u003e property in the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file, using the \u003ccode\u003eNO_PROXY\u003c/code\u003e environment variable to list hosts.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eNO_PROXY\u003c/code\u003e setting in \u003ccode\u003elogger.EnvVars\u003c/code\u003e accepts a comma-separated list of hosts that should bypass the proxy during logging, as supported by Fluent Bit.\u003c/p\u003e\n"],["\u003cp\u003eAfter modifying \u003ccode\u003eoverrides.yaml\u003c/code\u003e, changes must be applied using the command \u003ccode\u003eapigeectl apply --telemetry -f overrides.yaml\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# Logging with HTTP proxy forwarding enabled\n\n| You are currently viewing version 1.9 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\nLogging when HTTP proxy forwarding is enabled\n---------------------------------------------\n\n\nWhen you enable HTTP proxy forwarding, you create a single point through which multiple machines\nsend requests to an external server. For logging, you may not want to have all traffic forwarded\nthrough the proxy.\n\n\nThis procedure explains how to disable HTTP proxy forwarding for specific hosts in your\noverrides file.\n\n### Procedure\n\n1. Disable proxy forwarding for logging for specific hosts by setting the `logger.EnvVars` property in `overrides.yaml`: \n\n ```\n logger:\n ...\n EnvVars:\n NO_PROXY: '\u003ccomma-separated-values\u003e'\n ```\n\n for example: \n\n ```\n EnvVars:\n NO_PROXY: 'kubernetes.default.svc,oauth2.googleapis.com,logging.googleapis.com'\n ```\n\n\n The `logger.EnvVars` property allows you to pass in environment variables\n supported by Fluent Bit. See\n [NO_PROXY](https://docs.fluentbit.io/manual/administration/http-proxy#no_proxy)\n in the Fluent Bit documentation.\n2. Apply the changes to logger with `apigeectl apply` with the `--telemetry` scope: \n\n ```\n apigeectl apply --telemetry -f overrides.yaml\n ```\n\n### See also\n\n- [`logger.EnvVars`](/apigee/docs/hybrid/v1.9/config-prop-ref#logger-envvars) in the Configuration properties reference.\n- [Configure forward proxying for API proxies](/apigee/docs/hybrid/v1.9/forward-proxy)."]]
