- Packetbeat Reference: other versions:
- Overview
- Getting Started With Packetbeat
- Running Packetbeat on Docker
- Upgrading Packetbeat
- Configuring Packetbeat
- Configuration Options (Reference)
- Processors
- Setting Traffic Capturing Options
- Filtering and Enhancing the Exported Data
- Configuring Packetbeat to Use Ingest Node
- Exporting GeoIP Information
- Configuring Packetbeat to Use Logstash
- Configuring Flows to Monitor Network Traffic
- Using Environment Variables in the Configuration
- Configuring Thrift-RPC Support
- Maintaining the Real-Time State of the Network Topology
- YAML Tips and Gotchas
- Exported Fields
- AMQP Fields
- Beat Fields
- Cassandra Fields
- Cloud Provider Metadata Fields
- Common Fields
- DNS Fields
- Flow Event Fields
- HTTP Fields
- ICMP Fields
- Memcache Fields
- MongoDb Fields
- MySQL Fields
- NFS Fields
- PostgreSQL Fields
- Raw Fields
- Redis Fields
- Thrift-RPC Fields
- Transaction Event Fields
- Measurements (Transactions) Fields
- Securing Packetbeat
- Visualizing Packetbeat Data in Kibana
- Troubleshooting
- Developer Guide: Adding a New Protocol
WARNING: Version 5.4 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.
Raw Fields
editRaw Fields
editThese fields contain the raw transaction data.
request
edittype: text
For text protocols, this is the request as seen on the wire (application layer only). For binary protocols this is our representation of the request.
response
edittype: text
For text protocols, this is the response as seen on the wire (application layer only). For binary protocols this is our representation of the request.
Was this helpful?
Thank you for your feedback.