WARNING: Version 6.0 of Packetbeat has passed its EOL date.

This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.

« Capture Cassandra traffic Capture MySQL and PgSQL traffic »

› › ›

Capture Memcache traffic

edit

Capture Memcache traffic

edit

The memcache section of the packetbeat.yml config file specifies configuration options for the memcache protocol. Here is a sample configuration section for memcache:

packetbeat.protocols:
- type: memcache
  ports: [11211]
  parseunknown: false
  maxvalues: 0
  maxbytespervalue: 100
  transaction_timeout: 200
  udptransactiontimeout: 200

Configuration options

edit

Also see Common protocol options.

`parseunknown`

edit

When this option is enabled, it forces the memcache text protocol parser to accept unknown commands.

The unknown commands MUST NOT contain a data part.

`maxvalues`

edit

The maximum number of values to store in the message (multi-get). All values will be base64 encoded.

The possible settings for this option are:

maxvalue: -1, which stores all values (text based protocol multi-get)
maxvalue: 0, which stores no values (default)
maxvalue: N, which stores up to N values

`maxbytespervalue`

edit

The maximum number of bytes to be copied for each value element.

Values will be base64 encoded, so the actual size in the JSON document will be 4 times the value that you specify for maxbytespervalue.

`udptransactiontimeout`

edit

The transaction timeout in milliseconds. The defaults is 10000 milliseconds.

Quiet messages in UDP binary protocol get responses only if there is an error. The memcache protocol analyzer will wait for the number of milliseconds specified by udptransactiontimeout before publishing quiet messages. Non-quiet messages or quiet requests with an error response are published immediately.

« Capture Cassandra traffic Capture MySQL and PgSQL traffic »