- 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
- Configure index lifecycle management
- Specify SSL settings
- Filter and enhance the exported data
- Define processors
- Add cloud metadata
- Add fields
- Add labels
- Add the local time zone
- Add tags
- Decode JSON fields
- Decode Base64 fields
- Decompress gzip fields
- Community ID Network Flow Hash
- Convert
- Drop events
- Drop fields from events
- Extract array
- Keep fields from events
- Registered Domain
- Rename fields from events
- Add Kubernetes metadata
- Add Docker metadata
- Add Host metadata
- Add Observer metadata
- Dissect strings
- DNS Reverse Lookup
- Add process metadata
- Parse data by using ingest node
- Enrich events with geoIP information
- Configure project paths
- Configure 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
- DHCPv4 fields
- DNS fields
- Docker fields
- ECS fields
- Flow Event fields
- Host fields
- HTTP fields
- ICMP fields
- Jolokia Discovery autodiscover provider fields
- Kubernetes fields
- Memcache fields
- MongoDb fields
- MySQL fields
- NFS fields
- PostgreSQL fields
- Process 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
- Get help
- Debug
- Record a trace
- Common problems
- Dashboard in Kibana is breaking up data fields incorrectly
- Packetbeat doesn’t see any packets when using mirror ports
- Packetbeat can’t capture traffic from Windows loopback interface
- Packetbeat is missing long running transactions
- Packetbeat isn’t capturing MySQL performance data
- Packetbeat uses too much bandwidth
- Error loading config file
- Found unexpected or unknown characters
- Logstash connection doesn’t work
- @metadata is missing in Logstash
- Not sure whether to use Logstash or Beats
- SSL client fails to connect to Logstash
- Monitoring UI shows fewer Beats than expected
- Fields show up as nested JSON in Kibana
- Contributing to Beats
Memcache fields
editMemcache fields
editMemcached-specific event fields
-
memcache.protocol_type -
The memcache protocol implementation. The value can be "binary" for binary-based, "text" for text-based, or "unknown" for an unknown memcache protocol type.
type: keyword
-
memcache.request.line -
The raw command line for unknown commands ONLY.
type: keyword
-
memcache.request.command -
The memcache command being requested in the memcache text protocol. For example "set" or "get". The binary protocol opcodes are translated into memcache text protocol commands.
type: keyword
-
memcache.response.command -
Either the text based protocol response message type or the name of the originating request if binary protocol is used.
type: keyword
-
memcache.request.type -
The memcache command classification. This value can be "UNKNOWN", "Load", "Store", "Delete", "Counter", "Info", "SlabCtrl", "LRUCrawler", "Stats", "Success", "Fail", or "Auth".
type: keyword
-
memcache.response.type -
The memcache command classification. This value can be "UNKNOWN", "Load", "Store", "Delete", "Counter", "Info", "SlabCtrl", "LRUCrawler", "Stats", "Success", "Fail", or "Auth". The text based protocol will employ any of these, whereas the binary based protocol will mirror the request commands only (see
memcache.response.statusfor binary protocol).type: keyword
-
memcache.response.error_msg -
The optional error message in the memcache response (text based protocol only).
type: keyword
-
memcache.request.opcode -
The binary protocol message opcode name.
type: keyword
-
memcache.response.opcode -
The binary protocol message opcode name.
type: keyword
-
memcache.request.opcode_value -
The binary protocol message opcode value.
type: long
-
memcache.response.opcode_value -
The binary protocol message opcode value.
type: long
-
memcache.request.opaque -
The binary protocol opaque header value used for correlating request with response messages.
type: long
-
memcache.response.opaque -
The binary protocol opaque header value used for correlating request with response messages.
type: long
-
memcache.request.vbucket -
The vbucket index sent in the binary message.
type: long
-
memcache.response.status -
The textual representation of the response error code (binary protocol only).
type: keyword
-
memcache.response.status_code -
The status code value returned in the response (binary protocol only).
type: long
-
memcache.request.keys -
The list of keys sent in the store or load commands.
type: array
-
memcache.response.keys -
The list of keys returned for the load command (if present).
type: array
-
memcache.request.count_values -
The number of values found in the memcache request message. If the command does not send any data, this field is missing.
type: long
-
memcache.response.count_values -
The number of values found in the memcache response message. If the command does not send any data, this field is missing.
type: long
-
memcache.request.values -
The list of base64 encoded values sent with the request (if present).
type: array
-
memcache.response.values -
The list of base64 encoded values sent with the response (if present).
type: array
-
memcache.request.bytes -
The byte count of the values being transferred.
type: long
format: bytes
-
memcache.response.bytes -
The byte count of the values being transferred.
type: long
format: bytes
-
memcache.request.delta -
The counter increment/decrement delta value.
type: long
-
memcache.request.initial -
The counter increment/decrement initial value parameter (binary protocol only).
type: long
-
memcache.request.verbosity -
The value of the memcache "verbosity" command.
type: long
-
memcache.request.raw_args -
The text protocol raw arguments for the "stats …" and "lru crawl …" commands.
type: keyword
-
memcache.request.source_class -
The source class id in slab reassign command.
type: long
-
memcache.request.dest_class -
The destination class id in slab reassign command.
type: long
-
memcache.request.automove -
The automove mode in the slab automove command expressed as a string. This value can be "standby"(=0), "slow"(=1), "aggressive"(=2), or the raw value if the value is unknown.
type: keyword
-
memcache.request.flags -
The memcache command flags sent in the request (if present).
type: long
-
memcache.response.flags -
The memcache message flags sent in the response (if present).
type: long
-
memcache.request.exptime -
The data expiry time in seconds sent with the memcache command (if present). If the value is <30 days, the expiry time is relative to "now", or else it is an absolute Unix time in seconds (32-bit).
type: long
-
memcache.request.sleep_us -
The sleep setting in microseconds for the lru_crawler sleep command.
type: long
-
memcache.response.value -
The counter value returned by a counter operation.
type: long
-
memcache.request.noreply -
Set to true if noreply was set in the request. The
memcache.responsefield will be missing.type: boolean
-
memcache.request.quiet -
Set to true if the binary protocol message is to be treated as a quiet message.
type: boolean
-
memcache.request.cas_unique -
The CAS (compare-and-swap) identifier if present.
type: long
-
memcache.response.cas_unique -
The CAS (compare-and-swap) identifier to be used with CAS-based updates (if present).
type: long
-
memcache.response.stats -
The list of statistic values returned. Each entry is a dictionary with the fields "name" and "value".
type: array
-
memcache.response.version -
The returned memcache version string.
type: keyword