See #683 for a similar concept. In addition to encrypting/decrypting the data streams, Cryostat should also offer the ability to (de)compress data sent to or retrieved from object storage. This would primarily be useful for reducing the disk space consumption of JFR files.
If/when combined with #683, the flow should be raw -> compressed -> encrypted -> uploaded, and likewise downloaded -> decrypted -> decompressed -> processed. Encrypted data should not really be compressible, so any compression gains should be expected on the raw data.
Describe the feature
See #683 for a similar concept. In addition to encrypting/decrypting the data streams, Cryostat should also offer the ability to (de)compress data sent to or retrieved from object storage. This would primarily be useful for reducing the disk space consumption of JFR files.
If/when combined with #683, the flow should be
raw -> compressed -> encrypted -> uploaded, and likewisedownloaded -> decrypted -> decompressed -> processed. Encrypted data should not really be compressible, so any compression gains should be expected on the raw data.See also https://github.com/cryostatio/cryostat-legacy/issues/732 See also https://github.com/cryostatio/cryostat/issues/269
Anything other information?
No response