Changing log compression formats
Last updated 2023-09-28
Fastly's Real-Time Log Streaming feature allows you to specify compression format and options for file-based logging endpoints. These include the Azure Blob, FTP, Google Cloud Storage, Kafka, OpenStack, Amazon S3, SFTP, Digital Ocean, and Cloud Files logging endpoints.
Although the default is to use no compression, we allow you to choose one of several compression mechanisms:
- Zstandard, a compression algorithm defined by RFC 8478
- Snappy, a compression and decompression library used by many Google products as referenced in the Snappy compressed format description
- Gzip, a compression utility as defined in RFC 1952 and RFC 1951
- Web interface
If you're using Gzip compression, the web interface defaults to a Gzip compression level of 3 and can only be changed using the Logging API. If the Gzip compression level has been set to a value other than
3 via an API call, then that level is displayed as a read-only value.
Follow these instructions to update a file-based logging endpoint's compression format using the web interface:
- Log in to the Fastly web interface.
- From the Home page, select the appropriate service. You can use the search box to search by ID, name, or domain.
- Click Edit configuration and then select the option to clone the active version.
Click the name of a file-based logging endpoint you want to edit.
Click Advanced options near the bottom of the page.
In the Compression section, select a compression format for the logging endpoint.
- Click Activate to deploy your configuration changes.