- Packetbeat Reference: other versions:
- Overview
- Getting started with Packetbeat
- Setting up and running Packetbeat
- Upgrading Packetbeat
- Configuring Packetbeat
- Set traffic capturing options
- Set up flows to monitor network traffic
- Specify which transaction protocols to monitor
- Specify which processes to monitor
- Specify general settings
- Configure the internal queue
- Configure the output
- Specify SSL settings
- Filter and enhance the exported data
- Parse data by using ingest node
- Export GeoIP Information
- Set up project paths
- Set up the Kibana endpoint
- Load the Kibana dashboards
- Load the Elasticsearch index template
- Configure logging
- Use environment variables in the configuration
- YAML tips and gotchas
- HTTP Endpoint
- packetbeat.reference.yml
- Exported fields
- AMQP fields
- Beat fields
- Cassandra fields
- Cloud provider metadata fields
- Common fields
- DNS fields
- Docker fields
- Flow Event fields
- Host fields
- HTTP fields
- ICMP fields
- Kubernetes fields
- Memcache fields
- MongoDb fields
- MySQL fields
- NFS fields
- PostgreSQL fields
- Raw fields
- Redis fields
- Thrift-RPC fields
- TLS fields
- Transaction Event fields
- Measurements (Transactions) fields
- Monitoring Packetbeat
- Securing Packetbeat
- Visualizing Packetbeat data in Kibana
- Troubleshooting
- Contributing to Beats
Capture Memcache traffic
editCapture Memcache traffic
editThe 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
editAlso see Common protocol options.
parseunknown
editWhen 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
editThe 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
editThe 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
editThe 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.