When you enable HTTP proxy forwarding, you create a single point through which multiple machines
send requests to an external server. For logging, you may not want to have all traffic forwarded
through the proxy.
This procedure explains how to disable HTTP proxy forwarding for specific hosts in your
overrides file.
Procedure
Disable proxy forwarding for logging for specific hosts by setting the
logger.envVars property in overrides.yaml:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eEnabling HTTP proxy forwarding creates a single point for multiple machines to send requests to an external server, which might not be ideal for logging purposes.\u003c/p\u003e\n"],["\u003cp\u003eYou can disable HTTP proxy forwarding for specific hosts by modifying 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 environment variable within \u003ccode\u003elogger.envVars\u003c/code\u003e allows specifying comma-separated hosts that should bypass the HTTP proxy.\u003c/p\u003e\n"],["\u003cp\u003eAfter updating the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file, changes must be applied using the \u003ccode\u003eapigee-telemetry\u003c/code\u003e chart with the \u003ccode\u003ehelm upgrade\u003c/code\u003e command, or the \u003ccode\u003ehelm install\u003c/code\u003e command if there are no deployments.\u003c/p\u003e\n"]]],[],null,["# Logging with HTTP proxy forwarding enabled\n\n| You are currently viewing version 1.12 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`](/apigee/docs/hybrid/v1.12/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.12/config-prop-ref#logger-envvars) in the Configuration properties reference.\n- [Configure forward proxying for API proxies](/apigee/docs/hybrid/v1.12/forward-proxy)."]]