Cuando habilitas el reenvío de proxy HTTP, creas un punto único a través del cual varias máquinas envían solicitudes a un servidor externo. Para los registros, es posible que no desees que todo el tráfico se reenvíe a través del proxy.
En este procedimiento, se explica cómo inhabilitar el reenvío del proxy HTTP para hosts específicos en el archivo de anulación.
Procedimiento
Para inhabilitar el reenvío de proxy para el registro de hosts específicos, configura la propiedad logger.envVars en overrides.yaml:
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (UTC)"],[],[],null,["# Logging with HTTP proxy forwarding enabled\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.15/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.15/config-prop-ref#logger-envvars) in the Configuration properties reference.\n- [Configure forward proxying for API proxies](/apigee/docs/hybrid/v1.15/forward-proxy)."]]
