Logstash HTTP Output: Configure Proxy Authentication

Use the plugin's URL-plus-account proxy object in the output pipeline, preserving the real collector URL and event format.

output {
  http {
    url => "${EVENT_ENDPOINT}"
    http_method => "post"
    format => "json"
    proxy => {
      url => "${OUTBOUND_PROXY_URL}"
      user => "${OUTBOUND_PROXY_USER}"
      password => "${OUTBOUND_PROXY_PASSWORD}"
    }
  }
}

Set these values in the Logstash service's launch environment before it loads the pipeline. EVENT_ENDPOINT remains the collector; OUTBOUND_PROXY_URL can be http://proxy.example:8080 even for an HTTPS collector. A later export in another shell does not change the running output.

The plugin accepts a URI string, a hash with host/port/scheme, or the shown hash with url and optional user/password. Choose one form and keep its field names together. The URI-string form can use a candidate from the HTTP proxy list for a public route that needs no proxy account.

Merge this with the existing HTTP-delivery pipeline and retain its collector authentication and event format. The object account logs in to the intermediary; the collector's token or API login still belongs to the destination request.

Winndannde jowitiiɗe heen