Capture Redis traffic
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
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
Also see Common protocol options.
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 request pipelining while at the same time limiting the amount of memory consumed by replication sessions.