Logging when HTTP proxy forwarding is enabled

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

1. Disable proxy forwarding for logging for specific hosts by setting thelogger.envVars property inoverrides.yaml:

   logger:...  envVars:    NO_PROXY: '<comma-separated-values>'

   for example:

     envVars:    NO_PROXY: 'kubernetes.default.svc,oauth2.googleapis.com,logging.googleapis.com'

   Thelogger.envVars property allows you to pass in environment variables supported by Fluent Bit. SeeNO_PROXY in the Fluent Bit documentation.

2. Apply the changes with theapigee-telemetry chart:

   helm upgrade telemetry apigee-telemetry/ \  --namespace apigee \  --atomic \  -fOVERRIDES_FILE

   Note: If you see an error sayingError: UPGRADE FAILED: "telemetry" has no deployed releases, replaceupgrade withinstall and try the command again.

See also

• logger.envVars in the Configuration properties reference.
• Configure forward proxying for API proxies.