-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
support the compressing stream in forward and secure forward #504
Comments
For secure forward, please check fluent-plugin-secure-forward: https://github.com/tagomoris/fluent-plugin-secure-forward |
We will consider supporting compression in v0.14's new APIs: #309 (comment) |
+1, this would be a great feature to help reduce our bandwidth charges on AWS |
Yes, I was just looking for this. You would need to support it in I have a use case where the compressed logs are ~10% of the uncompressed logs. For LAN, that doesn't matter, but for shipping inter-DC or to the cloud, that is a huge deal. +1 |
@deitch Do you use Gzip or Snappy like compression? |
Don't actually care. We have gotten similar results with gzip and plain zip. But as long as in_forward / in_secure_forward and out_forward both support it, I can put a fluentd on each host to collect and forward, and have another cluster of them in the cloud, and everyone is happy. |
+1 |
Does someone try this patch? |
I am looking for a option to compress a message during out_forward. Could someone help me? |
refer #1179 |
It's to save the bandwidth across the data centers, also accelerate the transfer speed and save the time.
The text was updated successfully, but these errors were encountered: