From a65c745994d11ea55148204aa651836a4f857f98 Mon Sep 17 00:00:00 2001 From: "panagiotis@rancher.com" Date: Tue, 29 Oct 2019 12:13:30 +0000 Subject: [PATCH] clarified what log severity means when syslog logging is selected Signed-off-by: panagiotis@rancher.com --- .../v2.x/en/cluster-admin/tools/logging/syslog/_index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/rancher/v2.x/en/cluster-admin/tools/logging/syslog/_index.md b/content/rancher/v2.x/en/cluster-admin/tools/logging/syslog/_index.md index f6f0a6acae1..e5aa8f8482f 100644 --- a/content/rancher/v2.x/en/cluster-admin/tools/logging/syslog/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/tools/logging/syslog/_index.md @@ -21,6 +21,8 @@ If you are using rsyslog, please make sure your rsyslog authentication mode is ` 1. Select a **Log Severity** for events that are logged to the Syslog server. For more information on each severity level, see the [Syslog protocol documentation](https://tools.ietf.org/html/rfc5424#page-11). + - By specifying a **Log Severity** does not mean that will act as a filtering mechanism for logs. To do that you should use a parser on the Syslog server. + ## Encryption Configuration If your Syslog server is using **TCP** protocol and uses TLS, you need to select **Use TLS** and complete the **Encryption Configuration** form.