Client Fields
editClient Fields
editA client is defined as the initiator of a network connection for events regarding sessions, connections, or bidirectional flow records.
For TCP events, the client is the initiator of the TCP connection that sends the SYN packet(s). For other protocols, the client is generally the initiator or requestor in the network transaction. Some systems use the term "originator" to refer the client in TCP connections. The client fields describe details about the system acting as the client in the network event. Client fields are usually populated in conjunction with server fields. Client fields are generally not populated for packet-level events.
Client / server representations can add semantic context to an exchange, which is helpful to visualize the data in certain situations. If your context falls in that category, you should still ensure that source and destination are filled appropriately.
Client Field Details
editField | Description | Level |
---|---|---|
client.address |
Some event client addresses are defined ambiguously. The event will sometimes list an IP, a domain or a unix socket. You should always store the raw address in the Then it should be duplicated to type: keyword |
extended |
client.bytes |
Bytes sent from the client to the server. type: long example: |
core |
client.domain |
Client domain. type: keyword |
core |
client.ip |
IP address of the client. Can be one or multiple IPv4 or IPv6 addresses. type: ip |
core |
client.mac |
MAC address of the client. type: keyword |
core |
client.packets |
Packets sent from the client to the server. type: long example: |
core |
client.port |
Port of the client. type: long |
core |
Field Reuse
editField sets that can be nested under Client
editNested fields | Description |
---|---|
Fields describing a location. |
|
Fields to describe the user relevant to the event. |