Como gerar registros quando o encaminhamento de proxy HTTP está ativado
Ao ativar o encaminhamento de proxy HTTP, você cria um único ponto pelo qual várias máquinas
enviam solicitações para um servidor externo. Para a geração de registros, talvez você não queira que todo o tráfego seja encaminhado
por meio do proxy.
Neste procedimento, explicamos como desativar o encaminhamento de proxy HTTP para hosts específicos no
arquivo de substituições.
Procedimento
Desative o encaminhamento de proxy para a geração de registros de hosts específicos definindo a
propriedade logger.EnvVars em overrides.yaml:
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-09-04 UTC."],[[["\u003cp\u003eHTTP proxy forwarding can be disabled for specific hosts to prevent all traffic from being routed through the proxy during logging.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003elogger.envVars\u003c/code\u003e property in the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file is used to define hosts that should bypass HTTP proxy forwarding.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eNO_PROXY\u003c/code\u003e environment variable, within \u003ccode\u003elogger.envVars\u003c/code\u003e, accepts a comma-separated list of host values to exclude from proxy forwarding.\u003c/p\u003e\n"],["\u003cp\u003eChanges to proxy forwarding configurations are applied using the \u003ccode\u003eapigee-telemetry\u003c/code\u003e chart via the \u003ccode\u003ehelm upgrade\u003c/code\u003e or \u003ccode\u003ehelm install\u003c/code\u003e command.\u003c/p\u003e\n"]]],[],null,["# Logging with HTTP proxy forwarding enabled\n\n| You are currently viewing version 1.13 of the Apigee hybrid documentation. 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`](/apigee/docs/hybrid/v1.13/config-prop-ref#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 with the `apigee-telemetry` chart: \n\n ```\n helm upgrade telemetry apigee-telemetry/ \\\n --namespace apigee \\\n --atomic \\\n -f OVERRIDES_FILE\n ```\n | **Note:** If you see an error saying `Error: UPGRADE FAILED: \"telemetry\" has no deployed releases`, replace `upgrade` with `install` and try the command again.\n\n### See also\n\n- [`logger.envVars`](/apigee/docs/hybrid/v1.13/config-prop-ref#logger-envvars) in the Configuration properties reference.\n- [Configure forward proxying for API proxies](/apigee/docs/hybrid/v1.13/forward-proxy)."]]
