Logging with HTTP proxy forwarding enabled

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 the logger.envVars property in overrides.yaml: 
    logger:
...
  envVars:
    NO_PROXY: '<comma-separated-values>'

    for example: 

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

    The logger.envVars property allows you to pass in environment variables supported by Fluent Bit. See NO_PROXY in the Fluent Bit documentation.

  2. Apply the changes to logger with apigeectl apply with the --telemetry scope: 
    apigeectl apply --telemetry -f overrides.yaml

See also