> [!CAUTION]
> You are currently viewing version 1.15 of the Apigee hybrid documentation. For more information, see [Supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions).

<button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">Version 1.15 </button>

- Supported versions:
- [v1.17 (latest)](https://docs.cloud.google.com/apigee/docs/hybrid/v1.17/open-telemetry-with-http-proxy-forwarding-enabled.md.txt)
- [v1.16](https://docs.cloud.google.com/apigee/docs/hybrid/v1.16/open-telemetry-with-http-proxy-forwarding-enabled.md.txt)
- [v1.15](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/open-telemetry-with-http-proxy-forwarding-enabled.md.txt)
- [v1.14](https://docs.cloud.google.com/apigee/docs/hybrid/v1.14/open-telemetry-with-http-proxy-forwarding-enabled.md.txt)
- [List of supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions)
- Unsupported versions:
- [v1.13](https://docs.cloud.google.com/apigee/docs/hybrid/v1.13/open-telemetry-with-http-proxy-forwarding-enabled.md.txt)
- [v1.12](https://docs.cloud.google.com/apigee/docs/hybrid/v1.12/open-telemetry-with-http-proxy-forwarding-enabled.html)
- [v1.11](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/open-telemetry-with-http-proxy-forwarding-enabled.html)
- [v1.10](https://docs.cloud.google.com/apigee/docs/hybrid/v1.10/open-telemetry-with-http-proxy-forwarding-enabled.html)
- [v1.9](https://docs.cloud.google.com/apigee/docs/hybrid/v1.9/open-telemetry-with-http-proxy-forwarding-enabled.html)
- [v1.8](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/open-telemetry-with-http-proxy-forwarding-enabled.html)
- [v1.7](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/open-telemetry-with-http-proxy-forwarding-enabled.html)
- [v1.6](https://docs.cloud.google.com/apigee/docs/hybrid/v1.6/open-telemetry-with-http-proxy-forwarding-enabled.html)
- [v1.5](https://docs.cloud.google.com/apigee/docs/hybrid/v1.5/open-telemetry-with-http-proxy-forwarding-enabled.html)
- [v1.4](https://docs.cloud.google.com/apigee/docs/hybrid/v1.4/open-telemetry-with-http-proxy-forwarding-enabled.html)
- [v1.3](https://docs.cloud.google.com/apigee/docs/hybrid/v1.3/open-telemetry-with-http-proxy-forwarding-enabled.html)
- [v1.2](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/open-telemetry-with-http-proxy-forwarding-enabled.html)
- [v1.1](https://docs.cloud.google.com/apigee/docs/hybrid/v1.1/open-telemetry-with-http-proxy-forwarding-enabled.html)

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.

<br />

## 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 support](https://opentelemetry.io/docs/collector/configuration/#proxy-support)in the OpenTelemetry documentation for more details.

You can use the following values for the `metrics.collector.envVars` property:

- For an `http` proxy:

  ```
  metrics:
  ...
  collector:
    envVars:
      HTTP_PROXY: '<proxy-address>'
  ```

  for example:

  ```
    envVars:
      HTTP_PROXY: 'http://1.1.1.1:80'
  ```
- For an `https` proxy:

  ```
  metrics:
  ...
  collector:
    envVars:
      HTTPS_PROXY: '<proxy-address>'
  ```

  for example:

  ```
    envVars:
      HTTPS_PROXY: 'https://1.1.1.1:80'
  ```
- For addresses that must not use the proxy:

  ```
  metrics:
  ...
  collector:
    envVars:
      NO_PROXY: '<comma-separated-values>'
  ```

  for example:

  ```
    envVars:
      NO_PROXY: 'http://1.1.1.1:80, http://1.1.1.1:81'
  ```

## Apply the changes

Use the following command to apply the changes with the `apigee-telemetry` chart:

```
helm upgrade telemetry apigee-telemetry/ \
  --namespace APIGEE_NAMESPACE \
  --atomic \
  -f OVERRIDES_FILE
```

> [!NOTE]
> **Note:** If you see an error saying `Error: UPGRADE FAILED: "telemetry" has no deployed releases`, replace `upgrade` with `install` and try the command again.

## What's next

- See [`metrics.collector.envVars`](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/config-prop-ref.md.txt#logger-envVars) in the Configuration properties reference.
- Learn how to [Configure forward proxying for API proxies](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/forward-proxy.md.txt).