From 2ec310934ab1f5e6386aec870e21fe0317cebad8 Mon Sep 17 00:00:00 2001 From: "wangyongchao.bj" Date: Wed, 28 Jul 2021 10:56:23 +0800 Subject: [PATCH] docs: update url for log parser in how-to-import-kata-logs-with-fluentd.md fixed the log parser url to kata 2.x path (https://github.com/kata-containers/tests/tree/main) for the How to import Kata Containers logs into Fluentd Doc. Fixes #2335 Signed-off-by: wangyongchao.bj --- docs/how-to/how-to-import-kata-logs-with-fluentd.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/how-to/how-to-import-kata-logs-with-fluentd.md b/docs/how-to/how-to-import-kata-logs-with-fluentd.md index 4db5c4feca..40d5b6c6d5 100644 --- a/docs/how-to/how-to-import-kata-logs-with-fluentd.md +++ b/docs/how-to/how-to-import-kata-logs-with-fluentd.md @@ -178,7 +178,7 @@ sub-filter on, for instance, the `SYSLOG_IDENTIFIER` to differentiate the Kata c on the `PRIORITY` to filter out critical issues etc. Kata generates a significant amount of Kata specific information, which can be seen as -[`logfmt`](https://github.com/kata-containers/tests/tree/master/cmd/log-parser#logfile-requirements). +[`logfmt`](https://github.com/kata-containers/tests/tree/main/cmd/log-parser#logfile-requirements). data contained in the `MESSAGE` field. Imported as-is, there is no easy way to filter on that data in Kibana: