Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP Output Compression #4472

Closed
madisonleavo opened this issue Jul 26, 2018 · 0 comments
Closed

HTTP Output Compression #4472

madisonleavo opened this issue Jul 26, 2018 · 0 comments
Labels
feature request Requests for new plugin and for new features to existing plugins
Milestone

Comments

@madisonleavo
Copy link

madisonleavo commented Jul 26, 2018

Feature Request

Enable HTTP Compression for outgoing HTTP

Proposal:

Enable HTTP Compression for outgoing HTTP. Really only makes sense for POST with batched data.
Could be set similar to influxdb OUTPUT config (though 'identity' doesn't make sense in straight HTTP context). Might even be able to copy/paste code to implement from influxdb plugin.

## HTTP Content-Encoding for write request body, can be set to "gzip" to
## compress body or "identity" to apply no encoding.
  # content_encoding = "identity"

Current behavior:

Uncompressed body is the only option.

Desired behavior:

  1. Enable Compression (gzip, deflate, br, etc) through telegraf.conf
  2. Set correct Content-Encoding HTTP header to match chosen compression.
  3. Compress payload

Use case: [Why is this important (helps with prioritizing requests)]

We use Telegraf as sidecar for docker containers on machines that have terrible bandwidth. Every byte saved helps.

@danielnelson danielnelson added the feature request Requests for new plugin and for new features to existing plugins label Jul 27, 2018
@danielnelson danielnelson added this to the 1.9.0 milestone Oct 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Requests for new plugin and for new features to existing plugins
Projects
None yet
Development

No branches or pull requests

3 participants