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-03 UTC."],[[["\u003cp\u003eThis document describes how to disable HTTP proxy forwarding for specific hosts when logging in Apigee hybrid version 1.10.\u003c/p\u003e\n"],["\u003cp\u003eDisabling proxy forwarding for specific hosts is managed by setting the \u003ccode\u003elogger.EnvVars\u003c/code\u003e property in the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eNO_PROXY\u003c/code\u003e variable, within \u003ccode\u003elogger.EnvVars\u003c/code\u003e, is used to define a comma-separated list of hosts that should bypass proxy forwarding during logging.\u003c/p\u003e\n"],["\u003cp\u003eChanges to logger configurations require the use of the \u003ccode\u003eapigeectl apply\u003c/code\u003e command with the \u003ccode\u003e--telemetry\u003c/code\u003e scope.\u003c/p\u003e\n"]]],[],null,["# Logging with HTTP proxy forwarding enabled\n\n| You are currently viewing version 1.10 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.10/config-prop-ref#logger-envvars) in the Configuration properties reference.\n- [Configure forward proxying for API proxies](/apigee/docs/hybrid/v1.10/forward-proxy)."]]