IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

› ›

Server Fields

edit

Server Fields

edit

A Server is defined as the responder in a network connection for events regarding sessions, connections, or bidirectional flow records.

For TCP events, the server is the receiver of the initial SYN packet(s) of the TCP connection. For other protocols, the server is generally the responder in the network transaction. Some systems actually use the term "responder" to refer the server in TCP connections. The server fields describe details about the system acting as the server in the network event. Server fields are usually populated in conjunction with client fields. Server 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.

Server Field Details

edit

Field	Description	Level
server.address	Some event server 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 `.address` field. Then it should be duplicated to `.ip` or `.domain`, depending on which one it is. type: keyword	extended
server.bytes	Bytes sent from the server to the client. type: long example: `184`	core
server.domain	Server domain. type: keyword	core
server.ip	IP address of the server. Can be one or multiple IPv4 or IPv6 addresses. type: ip	core
server.mac	MAC address of the server. type: keyword	core
server.packets	Packets sent from the server to the client. type: long example: `12`	core
server.port	Port of the server. type: long	core

Field Reuse

edit

Field sets that can be nested under Server

edit

Nested fields	Description
server.geo.*	Fields describing a location.
server.user.*	Fields to describe the user relevant to the event.

« Related Fields Service Fields »