Goals

• Users can configure compression in the collector

Non-Goals

• Ensuring that the compression codec/binary is available on the node

Motivation

In case of a high log volume it is feasible to reduce the network load and avoid overloading external long-term logging solution by enabling compression in the collector. This leads to a more efficient usage of resources but can increase the resource usage of the node. Customer should be able to decide if they want to have compression enabled for the log-forwarding.

Alternatives

• none I'm aware of

Acceptance Criteria

• Compression can be enabled for the collector through the API

Risk and Assumptions

• Increased consumption of CPU through the collector
• Misconfiguration is possible (compression binary is not available on the node)

Documentation Considerations

• Document how to use it and which compression is available

Open Questions

Additional Notes

• gzip /bzip2 is already available in RHCOS.