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

« HTTP Fields Log Fields »

› ›

Interface Fields

edit

IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Interface Fields

edit

The interface fields are used to record ingress and egress interface information when reported by an observer (e.g. firewall, router, load balancer) in the context of the observer handling a network connection. In the case of a single observer interface (e.g. network sensor on a span port) only the observer.ingress information should be populated.

Interface Field Details

edit

Field Description Level

Field	Description	Level
interface.alias	Interface alias as reported by the system, typically used in firewall implementations for e.g. inside, outside, or dmz logical interface naming. type: keyword example: `outside`	extended
interface.id	Interface ID as reported by an observer (typically SNMP interface ID). type: keyword example: `10`	extended
interface.name	Interface name as reported by the system. type: keyword example: `eth0`	extended

interface.alias

Interface alias as reported by the system, typically used in firewall implementations for e.g. inside, outside, or dmz logical interface naming.

type: keyword

example: outside

extended

interface.id

Interface ID as reported by an observer (typically SNMP interface ID).

type: keyword

example: 10

extended

interface.name

Interface name as reported by the system.

type: keyword

example: eth0

extended

Field Reuse

edit

The interface fields are expected to be nested at: observer.egress.interface, observer.ingress.interface.

Note also that the interface fields are not expected to be used directly at the root of the events.

« HTTP Fields Log Fields »