Merge pull request #70343 from abrennan89/OBSDOCS-476

OBSDOCS-476: Fix minor formatting bug and additional improvements

Author: abrennan89

modules/cluster-logging-collector-log-forward-loki.adoc

@@ -1,8 +1,12 @@
+// Module included in the following assemblies:
+//
+// * logging/log_collection_forwarding/log-forwarding.adoc
+
 :_mod-docs-content-type: PROCEDURE
 [id="cluster-logging-collector-log-forward-loki_{context}"]
-= Forwarding logs to Loki
+= Forwarding logs to an external Loki logging system
 
-You can forward logs to an external Loki logging system in addition to, or instead of, the internal default {product-title} Elasticsearch instance.
+You can forward logs to an external Loki logging system in addition to, or instead of, the default log store.
 
 To configure log forwarding to Loki, you must create a `ClusterLogForwarder` custom resource (CR) with an output to Loki, and a pipeline that uses the output. The output to Loki can use the HTTP (insecure) or HTTPS (secure HTTP) connection.
 
@@ -24,27 +28,29 @@ metadata:
 spec:
   serviceAccountName: <service_account_name> <3>
   outputs:
-   - name: loki-insecure <4>
-     type: "loki" <5>
-     url: http://loki.insecure.com:3100 <6>
-     loki:
-        tenantKey: kubernetes.namespace_name
-        labelKeys: kubernetes.labels.foo
-   - name: loki-secure <7>
-     type: "loki"
-     url: https://loki.secure.com:3100
-     secret:
-        name: loki-secret <8>
-     loki:
-        tenantKey: kubernetes.namespace_name <9>
-        labelKeys: kubernetes.labels.foo <10>
+  - name: loki-insecure <4>
+    type: "loki" <5>
+    url: http://loki.insecure.com:3100 <6>
+    loki:
+      tenantKey: kubernetes.namespace_name
+      labelKeys:
+      - kubernetes.labels.foo
+  - name: loki-secure <7>
+    type: "loki"
+    url: https://loki.secure.com:3100
+    secret:
+      name: loki-secret <8>
+    loki:
+      tenantKey: kubernetes.namespace_name <9>
+      labelKeys:
+      - kubernetes.labels.foo <10>
   pipelines:
-   - name: application-logs <11>
-     inputRefs:  <12>
-     - application
-     - audit
-     outputRefs: <13>
-     - loki-secure
+  - name: application-logs <11>
+    inputRefs:  <12>
+    - application
+    - audit
+    outputRefs: <13>
+    - loki-secure
 ----
 <1> In legacy implementations, the CR name must be `instance`. In multi log forwarder implementations, you can use any name.
 <2> In legacy implementations, the CR namespace must be `openshift-logging`. In multi log forwarder implementations, you can use any namespace.
@@ -65,10 +71,9 @@ spec:
 Because Loki requires log streams to be correctly ordered by timestamp, `labelKeys` always includes the `kubernetes_host` label set, even if you do not specify it. This inclusion ensures that each stream originates from a single host, which prevents timestamps from becoming disordered due to clock differences on different hosts.
 ====
 
-
-. Create the CR object:
+. Apply the `ClusterLogForwarder` CR object by running the following command:
 +
 [source,terminal]
 ----
-$ oc create -f <file-name>.yaml
+$ oc apply -f <filename>.yaml
 ----