When you enable HTTP proxy forwarding, you create a single point through which multiple machines
send requests to an external server. If you are behind a corporate proxy or firewall, Apigee
may not be able to send metrics to Cloud Monitoring with its default settings. You can set and
modify settings directly in the OpenTelemetry collector to have its requests pass through the proxy server.
This topic describes how to configure the OpenTelemetry collector settings using one of the three available
environment variables:
NO_PROXY: Accepts a list of hostnames or IP addresses whose traffic should not flow through the HTTP proxy.
HTTP_PROXY: Accepts the URL of the proxy whose server is used for HTTP connections.
HTTPS_PROXY: Accepts the URL of the proxy whose server is used for HTTPS connections.
Configure OpenTelemetry collector settings
You can configure the OpenTelemetry collector settings to work with HTTP proxy forwarding by using the
metrics.collector.envVars property in overrides.yaml. The metrics.collector.envVars property
allows you to pass in the environment variables supported by OpenTelemetry. See
Proxy supportin the OpenTelemetry documentation for more details.
You can use the following values for the metrics.collector.envVars property:
[[["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-26 UTC."],[[["\u003cp\u003eEnabling HTTP proxy forwarding creates a central point for multiple machines to send requests to external servers, which can impact Apigee's ability to send metrics to Cloud Monitoring when behind a corporate proxy or firewall.\u003c/p\u003e\n"],["\u003cp\u003eYou can configure the OpenTelemetry collector to route requests through a proxy server using the \u003ccode\u003emetrics.collector.envVars\u003c/code\u003e property in \u003ccode\u003eoverrides.yaml\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eHTTP_PROXY\u003c/code\u003e and \u003ccode\u003eHTTPS_PROXY\u003c/code\u003e environment variables define the URL of the proxy server for HTTP and HTTPS connections, respectively.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eNO_PROXY\u003c/code\u003e variable allows you to specify a list of hostnames or IP addresses that should bypass the HTTP proxy.\u003c/p\u003e\n"],["\u003cp\u003eApplying the configuration changes requires using the helm command with either an \u003ccode\u003eupgrade\u003c/code\u003e or \u003ccode\u003einstall\u003c/code\u003e of the apigee-telemetry chart.\u003c/p\u003e\n"]]],[],null,["| You are currently viewing version 1.14 of the Apigee hybrid documentation. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nWhen you enable HTTP proxy forwarding, you create a single point through which multiple machines\nsend requests to an external server. If you are behind a corporate proxy or firewall, Apigee\nmay not be able to send metrics to Cloud Monitoring with its default settings. You can set and\nmodify settings directly in the OpenTelemetry collector to have its requests pass through the proxy server.\n\nThis topic describes how to configure the OpenTelemetry collector settings using one of the three available\nenvironment variables:\n\n- `NO_PROXY`: Accepts a list of hostnames or IP addresses whose traffic should not flow through the HTTP proxy.\n- `HTTP_PROXY`: Accepts the URL of the proxy whose server is used for HTTP connections.\n- `HTTPS_PROXY`: Accepts the URL of the proxy whose server is used for HTTPS connections.\n\n\u003cbr /\u003e\n\nConfigure OpenTelemetry collector settings\n\nYou can configure the OpenTelemetry collector settings to work with HTTP proxy forwarding by using the\n`metrics.collector.envVars` property in `overrides.yaml`. The `metrics.collector.envVars` property\nallows you to pass in the environment variables supported by OpenTelemetry. See [Proxy support](https://opentelemetry.io/docs/collector/configuration/#proxy-support)in the OpenTelemetry documentation for more details.\n\nYou can use the following values for the `metrics.collector.envVars` property:\n\n- For an `http` proxy: \n\n ```\n metrics:\n ...\n collector:\n envVars:\n HTTP_PROXY: '\u003cproxy-address\u003e'\n ```\n\n for example: \n\n ```\n envVars:\n HTTP_PROXY: 'http://1.1.1.1:80'\n ```\n- For an `https` proxy: \n\n ```\n metrics:\n ...\n collector:\n envVars:\n HTTPS_PROXY: '\u003cproxy-address\u003e'\n ```\n\n for example: \n\n ```\n envVars:\n HTTPS_PROXY: 'https://1.1.1.1:80'\n ```\n- For addresses that must not use the proxy: \n\n ```\n metrics:\n ...\n collector:\n envVars:\n NO_PROXY: '\u003ccomma-separated-values\u003e'\n ```\n\n for example: \n\n ```\n envVars:\n NO_PROXY: 'http://1.1.1.1:80, http://1.1.1.1:81'\n ```\n\nApply the changes\n\nUse the following command to apply the changes with the `apigee-telemetry` chart: \n\n```\nhelm upgrade telemetry apigee-telemetry/ \\\n --namespace APIGEE_NAMESPACE \\\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\nWhat's next\n\n- See [`metrics.collector.envVars`](/apigee/docs/hybrid/v1.14/config-prop-ref#logger-envVars) in the Configuration properties reference.\n- Learn how to [Configure forward proxying for API proxies](/apigee/docs/hybrid/v1.14/forward-proxy)."]]