Environmental Fields

Name of the Beat sending the events. If the shipper name is set in the configuration file, then that value is used. If it is not set, the hostname is used.

The hostname as returned by the operating system on which the Beat is running.

The name of the server that served the transaction.

The name of the server that initiated the transaction.

The name of the logical service that served the transaction.

The name of the logical service that initiated the transaction.

format: dotted notation.

The IP address of the server that served the transaction.

format: dotted notation.

The IP address of the server that initiated the transaction.

format: Dotted notation.

If the server initiating the transaction is a proxy, this field contains the original client IP address. For HTTP, for example, the IP address extracted from a configurable HTTP header, by default X-Forwarded-For. Unless this field is disabled, it always has a value, and it matches the client_ip for non proxy clients.

type: geo_point

example: 40.715, -74.011

The GeoIP location of the real_ip IP address or of the client_ip address if the real_ip is disabled. The field is a string containing the latitude and longitude separated by a comma.

format: dotted notation.

The layer 4 port of the process that initiated the transaction.

example: udp

The transport protocol used for the transaction. If not specified, then tcp is assumed.

format: dotted notation.

The layer 4 port of the process that served the transaction.

The name of the process that served the transaction.

The name of the process that initiated the transaction.

The software release of the service serving the transaction. This can be the commit id or a semantic version.

Arbitrary tags that can be set per Beat and per transaction type.