Merge pull request #70811 from libander/OBSDOCS-771

OBSDOCS-771 - Fix exported fields headers

Author: ShaunaDiaz

modules/cluster-logging-exported-fields-top-level-fields.adoc

@@ -9,6 +9,7 @@
 
 The top level fields may be present in every record.
 
+[discrete]
 == message
 
 The original log entry text, UTF-8 encoded. This field may be absent or empty if a non-empty `structured` field is present. See the description of `structured` for more.
@@ -17,6 +18,7 @@ The original log entry text, UTF-8 encoded. This field may be absent or empty if
 Data type:: text
 Example value:: `HAPPY`
 
+[discrete]
 == structured
 
 Original log entry as a structured object. This field may be present if the forwarder was configured to parse structured JSON logs. If the original log entry was a valid structured log, this field will contain an equivalent JSON structure. Otherwise this field will be empty or absent, and the `message` field will contain the original log message. The `structured` field can have any subfields that are included in the log message, there are no restrictions defined here.
@@ -25,6 +27,7 @@ Original log entry as a structured object. This field may be present if the forw
 Data type:: group
 Example value:: map[message:starting fluentd worker pid=21631 ppid=21618 worker=0 pid:21631 ppid:21618 worker:0]
 
+[discrete]
 == @timestamp
 
 A UTC value that marks when the log payload was created or, if the creation time is not known, when the log payload was first collected. The “@” prefix denotes a field that is reserved for a particular use. By default, most tools look for “@timestamp” with ElasticSearch.
@@ -33,27 +36,31 @@ A UTC value that marks when the log payload was created or, if the creation time
 Data type:: date
 Example value:: `2015-01-24 14:06:05.071000000 Z`
 
+[discrete]
 == hostname
 
 The name of the host where this log message originated. In a Kubernetes cluster, this is the same as `kubernetes.host`.
 
 [horizontal]
 Data type:: keyword
 
+[discrete]
 == ipaddr4
 
 The IPv4 address of the source server. Can be an array.
 
 [horizontal]
 Data type:: ip
 
+[discrete]
 == ipaddr6
 
 The IPv6 address of the source server, if available. Can be an array.
 
 [horizontal]
 Data type:: ip
 
+[discrete]
 == level
 
 The logging level from various sources, including `rsyslog(severitytext property)`, a Python logging module, and others.
@@ -80,13 +87,15 @@ Map the log levels or priorities of other logging systems to their nearest match
 Data type:: keyword
 Example value:: `info`
 
+[discrete]
 == pid
 
 The process ID of the logging entity, if available.
 
 [horizontal]
 Data type:: keyword
 
+[discrete]
 == service
 
 The name of the service associated with the logging entity, if available. For example, syslog's `APP-NAME` and rsyslog's `programname` properties are mapped to the service field.
@@ -101,13 +110,15 @@ Optional. An operator-defined list of tags placed on each log by the collector o
 [horizontal]
 Data type:: text
 
+[discrete]
 == file
 
 The path to the log file from which the collector reads this log entry. Normally, this is a path in the `/var/log` file system of a cluster node.
 
 [horizontal]
 Data type:: text
 
+[discrete]
 == offset
 
 The offset value. Can represent bytes to the start of the log line in the file (zero- or one-based), or log line numbers (zero- or one-based), so long as the values are strictly monotonically increasing in the context of a single log file. The values are allowed to wrap, representing a new version of the log file (rotation).