Feature Request
The Datadog output plugin currently only has support to use the http_proxy environment variable for an HTTP Proxy. The InfluxDB output plugin support this, as well as declaring an http_proxy config element directly in the output plugin section of the config fragment.
To be consistent, and to support folks that would rather declare the http proxy in the config file, this feature request is to add this same support into the Datadog output plugin.
Proposal:
Add support for an 'http_proxy' field in the config file for the Datadog output plugin.
Current behavior:
The http_proxy environment variable must be configured.
Desired behavior:
The HTTP Proxy can be configured in either the environment variable or in the Datadog output config file, with the config file taking precedence.
Use case:
Adding system environment variables is much harder in the corporate world than just adding a new narrowly-scoped config file.
Feature Request
The Datadog output plugin currently only has support to use the http_proxy environment variable for an HTTP Proxy. The InfluxDB output plugin support this, as well as declaring an http_proxy config element directly in the output plugin section of the config fragment.
To be consistent, and to support folks that would rather declare the http proxy in the config file, this feature request is to add this same support into the Datadog output plugin.
Proposal:
Add support for an 'http_proxy' field in the config file for the Datadog output plugin.
Current behavior:
The http_proxy environment variable must be configured.
Desired behavior:
The HTTP Proxy can be configured in either the environment variable or in the Datadog output config file, with the config file taking precedence.
Use case:
Adding system environment variables is much harder in the corporate world than just adding a new narrowly-scoped config file.