Remove cluster logging from Viewing Logs topics

Author: mburke5678

_topic_map.yml

@@ -1685,8 +1685,8 @@ Topics:
     File: cluster-logging-curator
   - Name: Maintenance and support
     File: cluster-logging-maintenance-support
-- Name: Viewing cluster logs
-  File: cluster-logging-viewing
+- Name: Viewing logs for a specific resource
+  File: viewing-resource-logs
 - Name: Viewing cluster logs in Kibana
   File: cluster-logging-visualizer
   Distros: openshift-enterprise,openshift-origin

logging/cluster-logging-viewing.adoc

@@ -0,0 +1,16 @@
+[id="vewing-resource-logs"]
+= Viewing logs for a resource
+include::modules/common-attributes.adoc[]
+:context: viewing-resource-logs
+
+toc::[]
+
+You can view the logs for various resources, such as builds, deployments, and pods by using the OpenShift CLI (oc) and the web console. 
+
+[NOTE]
+====
+Resource logs are a default feature that provides limited log viewing capability. To enhance your log retrieving and viewing experience, it is recommended that you install xref:../logging/cluster-logging.adoc#cluster-logging[{product-title} cluster logging]. Cluster logging aggregates all the logs from your {product-title} cluster, such as node system audit logs, application container logs, and infrastructure logs, into a dedicated log store.  You can then query, discover, and visualize your log data through the xref:../logging/cluster-logging-visualizer.adoc#cluster-logging-visualizer-using[Kibana interface]. Resource logs do not access the cluster logging log store. 
+====
+
+include::modules/viewing-resource-logs-cli-console.adoc[leveloffset=+1]
+

logging/viewing-resource-logs.adoc

@@ -0,0 +1,77 @@
+// Module included in the following assemblies:
+//
+// * logging/viewing-resource-logs.adoc
+// * nodes/pods/nodes-pods-viewing.adoc
+
+[id="viewing-resource-logs-cli-console_{context}"]
+= Viewing resource logs
+
+You can view the log for various resources in the OpenShift CLI (oc) and web console. Logs read from the tail, or end, of the log.
+
+.Prerequisites
+
+* Access to the OpenShift CLI (oc).
+
+.Procedure (UI)
+
+. In the {product-title} console, navigate to *Workloads* -> *Pods* or navigate to the pod through the resource you want to investigate. 
++
+[NOTE]
+====
+Some resources, such as builds, do not have pods to query directly. In such instances, you can locate the *Logs* link on the *Details* page for the resource.
+====
+
+. Select a project from the drop-down menu.
+
+. Click the name of the pod you want to investigate.
+
+. Click *Logs*. 
+
+.Procedure (CLI)
+
+** View the log for a specific pod:
++
+[source,terminal]
+----
+$ oc logs -f <pod_name> -c <container_name>
+----
++
+--
+where:
+
+`-f`:: Optional: Specifies that the output follows what is being written into the logs. 
+`<pod_name>`:: Specifies the name of the pod.
+`<container_name>`:: Optional: Specifies the name of a container. When a pod has more than one container, you must specify the container name.
+--
++
+For example:
++
+[source,terminal]
+----
+$ oc logs ruby-58cd97df55-mww7r
+----
++
+[source,terminal]
+----
+$ oc logs -f ruby-57f7f4855b-znl92 -c ruby
+----
++
+The contents of log files are printed out.
+
+** View the log for a specific resource:
++
+[source,terminal]
+----
+$ oc logs <object_type>/<resource_name> <1>
+----
+<1> Specifies the resource type and name.
++
+For example:
++
+[source,terminal]
+----
+$ oc logs deployment/ruby
+----
++
+The contents of log files are printed out.
+

modules/cluster-logging-viewing-logs-console.adoc

@@ -18,3 +18,6 @@ include::modules/nodes-pods-viewing-project.adoc[leveloffset=+1]
 
 include::modules/nodes-pods-viewing-usage.adoc[leveloffset=+1]
 
+include::modules/viewing-resource-logs-cli-console.adoc[leveloffset=+1]
+
+