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. Si estás detrás de un proxy o firewall empresarial, es posible que Apigee
no pueda enviar métricas a Cloud Monitoring con su configuración predeterminada. Puedes establecer y
modificar la configuración directamente en el recopilador de OpenTelemetry para que sus solicitudes pasen a través del servidor proxy.
En este tema, se describe cómo configurar el recopilador de OpenTelemetry con una de las tres
variables de entorno disponibles:
NO_PROXY: Acepta una lista de nombres de host o direcciones IP cuyo tráfico no debe pasar por el proxy HTTP.
HTTP_PROXY: Acepta la URL del proxy cuyo servidor se usa para las conexiones HTTP.
HTTPS_PROXY: Acepta la URL del proxy cuyo servidor se utiliza para conexiones HTTPS.
Establece la configuración del recopilador de OpenTelemetry
Puedes configurar el recopilador de OpenTelemetry para que funcione con el reenvío de proxy HTTP usando la propiedad
metrics.collector.EnvVars en overrides.yaml. La propiedad metrics.collector.EnvVars
te permite pasar las variables de entorno compatibles con OpenTelemetry. Consulta
Compatibilidad con proxy en la documentación de OpenTelemetry para obtener más detalles.
Puedes usar los siguientes valores para la propiedad metrics.collector.EnvVars:
[[["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-03 (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,["# OpenTelemetry collector with HTTP proxy forwarding enabled\n\n| 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------------------------------------------\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-----------------\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\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)."]]