RHDEVDOCS-4259 - GCP & minor eventrouter correction w/peer rev

Author: libander

logging/cluster-logging-external.adoc

@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-By default, the {logging} sends container and infrastructure logs to the default internal Elasticsearch log store defined in the `ClusterLogging` custom resource. However, it does not send audit logs to the internal store because it does not provide secure storage. If this default configuration meets your needs, you do not need to configure the Cluster Log Forwarder.
+By default, the {logging} sends container and infrastructure logs to the default internal log store defined in the `ClusterLogging` custom resource. However, it does not send audit logs to the internal store because it does not provide secure storage. If this default configuration meets your needs, you do not need to configure the Cluster Log Forwarder.
 
 To send logs to other log aggregators, you use the {product-title} Cluster Log Forwarder. This API enables you to send container, infrastructure, and audit logs to specific endpoints within or outside your cluster. In addition, you can send different types of logs to various systems so that various individuals can access each type. You can also enable Transport Layer Security (TLS) support to send logs securely, as required by your organization.
 
@@ -188,6 +188,7 @@ include::modules/cluster-logging-troubleshooting-loki-entry-out-of-order-errors.
 * xref:../logging/cluster-logging-exported-fields.adoc#cluster-logging-exported-fields-kubernetes_cluster-logging-exported-fields[Log Record Fields].
 * link:https://grafana.com/docs/loki/latest/configuration/[Configuring Loki server]
 
+include::modules/cluster-logging-collector-log-forward-gcp.adoc[leveloffset=+1]
 
 include::modules/cluster-logging-collector-log-forward-project.adoc[leveloffset=+1]
 

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

@@ -0,0 +1,59 @@
+// Module included in the following assemblies:
+// cluster-logging-external.adoc
+//
+
+:_content-type: PROCEDURE
+[id="cluster-logging-collector-log-forward-gcp_{context}"]
+= Forwarding logs to Google Cloud Platform (GCP)
+
+You can forward logs to link:https://cloud.google.com/logging/docs/basic-concepts[Google Cloud Logging] in addition to, or instead of, the internal default {product-title} log store.
+
+[NOTE]
+====
+Using this feature with Fluentd is not supported.
+====
+
+.Prerequisites
+* {logging-title-uc} Operator 5.5.1 and later
+
+.Procedure
+
+. Create a secret using your link:https://cloud.google.com/iam/docs/creating-managing-service-account-keys[Google service account key].
++
+[source,terminal,subs="+quotes"]
+----
+$ oc -n openshift-logging create secret generic gcp-secret --from-file google-application-credentials.json=_<your_service_account_key_file.json>_
+----
+. Create a `ClusterLogForwarder` Custom Resource YAML using the template below:
++
+[source,yaml]
+----
+apiVersion: "logging.openshift.io/v1"
+kind: "ClusterLogForwarder"
+metadata:
+  name: "instance"
+  namespace: "openshift-logging"
+spec:
+  outputs:
+    - name: gcp-1
+      type: googleCloudLogging
+      secret:
+        name: gcp-secret
+      googleCloudLogging:
+        projectId : "openshift-gce-devel" <1>
+        logId : "app-gcp" <2>
+  pipelines:
+    - name: test-app
+      inputRefs: <3>
+        - application
+      outputRefs:
+        - gcp-1
+----
+<1> Set either a `projectId`, `folderId`, `organizationId`, or `billingAccountId` field and its corresponding value, depending on where you want to store your logs in the link:https://cloud.google.com/resource-manager/docs/cloud-platform-resource-hierarchy[GCP resource hierarchy].
+<2> Set the value to add to the `logName` field of the link:https://cloud.google.com/logging/docs/reference/v2/rest/v2/LogEntry[Log Entry].
+<3> Specify which log types to forward by using the pipeline: `application`, `infrastructure`, or `audit`.
+
+[role="_additional-resources"]
+.Additional resources
+* link:https://cloud.google.com/billing/docs/concepts[Google Cloud Billing Documentation]
+* link:https://cloud.google.com/logging/docs/view/logging-query-language[Google Cloud Logging Query Language Documentation]

modules/cluster-logging-eventrouter-deploy.adoc

@@ -107,7 +107,7 @@ objects:
 parameters:
   - name: IMAGE <6>
     displayName: Image
-    value: "registry.redhat.io/openshift-logging/eventrouter-rhel8:v0.3"
+    value: "registry.redhat.io/openshift-logging/eventrouter-rhel8:v0.4"
   - name: CPU  <7>
     displayName: CPU
     value: "100m"
@@ -124,8 +124,8 @@ parameters:
 <4> Creates a config map in the `openshift-logging` project to generate the required `config.json` file.
 <5> Creates a deployment in the `openshift-logging` project to generate and configure the Event Router pod.
 <6> Specifies the image, identified by a tag such as `v0.3`.
-<7> Specifies the minimum amount of memory to allocate to the Event Router pod. Defaults to `128Mi`.
-<8> Specifies the minimum amount of CPU to allocate to the Event Router pod. Defaults to `100m`.
+<7> Specifies the minimum amount of CPU to allocate to the Event Router pod. Defaults to `100m`.
+<8> Specifies the minimum amount of memory to allocate to the Event Router pod. Defaults to `128Mi`.
 <9> Specifies the `openshift-logging` project to install objects in.
 
 . Use the following command to process and apply the template: