liveBook · Manning

Compression

As explained in Logs and Telemetry

Compression is the encoding of data into a representation that requires less storage or transmission capacity.

Compression encodes data into a representation that uses less transmission capacity. In HTTP output, enable it with the compress property; gzip is the available option, and both endpoints must support it. section 5.8

Compressing Fluent Bit HTTP output

Configure Fluent Bit's HTTP output with compression enabled and gzip selected when sending substantial JSON payloads. This is especially useful when traffic crosses data centers or passes through a proxy. section 5.8

Listing 5.10 HTTP output example: http-output.conf
[SERVICE]
  flush 1
  log_level error

[INPUT]
  name http    
  listen 0.0.0.0
  port 9881
  tag http-in

[OUTPUT]
  match *
  name http     #1
  port 8080     #2
  host 127.0.0.1
  uri /simple                  #3
  format json               #4
  header fluentbit http         #5
  json_date_format iso8601    #6

Inspect the HTTP output configuration alongside compression-related options such as format, headers, and destination settings. section 5.8

How Logs and Telemetry covers it

How deep it goes
Explains enabling compression through a property and identifies gzip as the available algorithm, requiring support at both endpoints.
Examples
Demonstrates compression for Fluent Bit HTTP output carrying JSON data through data-center or proxy-connected networks.
What it assumes
Assumes an HTTP sender and receiver that both support the selected compression algorithm.
What you can do after
Apply compression via Fluent Bit's HTTP output configuration using gzip.
How it connects
Connects HTTP payloads with JSON, gzip, proxies, and distributed network deployments.

Also explained in

Compare how 11 books explain compression →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Logs and Telemetry. The section links point to the parts of the book it draws on.