IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Capture TLS traffic Specify which processes to monitor »
Elastic Docs ›Packetbeat Reference [7.2] ›Configuring Packetbeat ›Specify which transaction protocols to monitor

Capture Redis traffic

edit

Capture Redis traffic

edit

The Redis protocol has several specific configuration options. Here is a sample configuration for the redis section of the packetbeat.yml config file:

packetbeat.protocols:
- type: redis
  ports: [6379]
  queue_max_bytes: 1048576
  queue_max_messages: 20000

Configuration options

edit

Also see Common protocol options.

queue_max_bytes and queue_max_messages

edit

In order for request/response correlation to work, Packetbeat needs to store requests in memory until a response is received. These settings impose a limit on the number of bytes (queue_max_bytes) and number of requests (queue_max_messages) that can be stored. These limits are per-connection. The default is to queue up to 1MB or 20.000 requests per connection, which allows to use request pipelining while at the same time limiting the amount of memory consumed by replication sessions.

« Capture TLS traffic Specify which processes to monitor »