You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Enable Compression (gzip, deflate, br, etc) through telegraf.conf
Set correct Content-Encoding HTTP header to match chosen compression.
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.
The text was updated successfully, but these errors were encountered:
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.
Current behavior:
Uncompressed body is the only option.
Desired behavior:
Content-Encoding
HTTP header to match chosen compression.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.
The text was updated successfully, but these errors were encountered: