Ordering content by weight (#8787)
* ordering content by weight * fix weight of 'setup' contents * fix weight of 'concepts' contents * fix weight of 'tasks' contents * fix weight of 'tutorials' contents * fix weight of 'reference' contents * Revert "fix weight of 'tasks' contents" This reverts commit 4b6916bed07c92c5f9eed75fb0a7ef0244266623. * Revert "fix weight of 'tutorials' contents" This reverts commit a1f783314337b1eb40017aef47a6bf1453d8c840. * Revert "fix weight of 'setup' contents" This reverts commit 91c8de366587eed25c803f8e7d5a59005adb6025. * Revert "fix weight of 'reference' contents" This reverts commit cc95605f6a9863f8a4ffb636178c69a80d302c3e.
This commit is contained in:
committed by
k8s-ci-robot
parent
874ebb8f0a
commit
0502832cbb
@@ -3,6 +3,7 @@ reviewers:
|
||||
- piosz
|
||||
- x13n
|
||||
title: Logging Architecture
|
||||
weight: 60
|
||||
---
|
||||
|
||||
Application and systems logs can help you understand what is happening inside your cluster. The logs are particularly useful for debugging problems and monitoring cluster activity. Most modern applications have some kind of logging mechanism; as such, most container engines are likewise designed to support some kind of logging. The easiest and most embraced logging method for containerized applications is to write to the standard output and standard error streams.
|
||||
|
||||
Reference in New Issue
Block a user