8.0

Table Of Contents
Formatting Framing UDP TCP SSL Comments
RFC 5424 Unspecified Supported
RFC 5426
Supported
RFC 5425
Supported
RFC 5424
Formatting of messages
complies to RFC 5424.
Framing defaults to octet-
counting with TCP or SSL (TLS).
With UDP, framing might not
be explicitly specified.
RFC 5424 Non_transparen
t
Forbidden Not Supported Not
Supported
Not supported because
embedded newlines in
structured data might create
corrupted messages.
RFC 5424 Octet_counting Forbidden Supported
RFC 5425
Supported
RFC 5425
Formatting of messages
complies to RFC 5424.
RFC 3164 Unspecified Supported
RFC 5426
Supported Supported Formatting of messages
complies to RFC 3164, only
timestamps are in RFC 3339
format.
Structured data is prepended to
each message.
Framing defaults to non-
transparent with TCP or SSL
(TLS) and embedded newlines
in structured data might corrupt
messages.
With UDP, packets are framed.
RFC 3164 Non_transparen
t
Forbidden Supported Supported Formatting of messages
complies to RFC 3164, only
timestamps are in RFC 3339
format.
Structured data is prepended to
each message.
Framing defaults to non-
transparent with TCP or SSL
(TLS) and embedded newlines
in structured data might corrupt
messages.
RFC 3164 Octet_counting Forbidden Supported
RFC 6587
Supported
RFC 6587
Formatting of messages
complies to RFC 3164, only
timestamps are in RFC 3339
format.
Structured data is prepended to
each message.
Log File Formats
Starting with ESXi 8.0, the format of log files is standardized and is expressed in Augmented
Backus-Naur Form (ABNF).
VMware ESXi Installation and Setup
VMware, Inc. 241