Skip to content

Commit f1b4131

Browse files
authored
Merge pull request #31538 from mbongard/patch-1
Fixed malformed sentence
2 parents 70a990d + 8ea2fb3 commit f1b4131

File tree

1 file changed

+1
-1
lines changed
  • content/en/docs/concepts/cluster-administration

1 file changed

+1
-1
lines changed

content/en/docs/concepts/cluster-administration/logging.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ weight: 60
1212
Application logs can help you understand what is happening inside your application. The logs are particularly useful for debugging problems and monitoring cluster activity. Most modern applications have some kind of logging mechanism. Likewise, container engines are designed to support logging. The easiest and most adopted logging method for containerized applications is writing to standard output and standard error streams.
1313

1414
However, the native functionality provided by a container engine or runtime is usually not enough for a complete logging solution.
15-
For example, you may want access your application's logs if a container crashes; a pod gets evicted; or a node dies.
15+
For example, you may want to access your application's logs if a container crashes, a pod gets evicted, or a node dies.
1616
In a cluster, logs should have a separate storage and lifecycle independent of nodes, pods, or containers. This concept is called _cluster-level logging_.
1717

1818
<!-- body -->

0 commit comments

Comments
 (0)