Skip to content

Commit 57202ea

Browse files
authored
Merge pull request #31138 from mburke5678/logging-update-viewing-follow
Update cluster logging from Viewing Logs topics
2 parents a34d856 + 22ca079 commit 57202ea

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

logging/viewing-resource-logs.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ You can view the logs for various resources, such as builds, deployments, and po
99

1010
[NOTE]
1111
====
12-
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.
12+
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[OpenShift Logging]. OpenShift 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 OpenShift Logging log store.
1313
====
1414

1515
include::modules/viewing-resource-logs-cli-console.adoc[leveloffset=+1]

modules/gathering-application-diagnostic-data.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
Application failures can occur within running application pods. In these situations, you can retrieve diagnostic information with these strategies:
99

1010
* Review events relating to the application pods.
11-
* Review the logs from the application pods, including application-specific log files that are not collected by the {product-title} logging framework.
11+
* Review the logs from the application pods, including application-specific log files that are not collected by the OpenShift Logging framework.
1212
* Test application functionality interactively and run diagnostic tools in an application container.
1313

1414
.Prerequisites
@@ -32,7 +32,7 @@ $ oc describe pod/my-app-1-akdlg
3232
$ oc logs -f pod/my-app-1-akdlg
3333
----
3434

35-
. Query specific logs within a running application pod. Logs that are sent to stdout are collected by the {product-title} logging framework and are included in the output of the preceding command. The following query is only required for logs that are not sent to stdout.
35+
. Query specific logs within a running application pod. Logs that are sent to stdout are collected by the OpenShift Logging framework and are included in the output of the preceding command. The following query is only required for logs that are not sent to stdout.
3636
+
3737
.. If an application log can be accessed without root privileges within a pod, concatenate the log file as follows:
3838
+

0 commit comments

Comments
 (0)