From dc98fa21a94293aff0923a64ec2767a409426663 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=A9r=C3=B4me=20Petazzoni?= Date: Wed, 15 Aug 2018 04:04:18 -0500 Subject: [PATCH] Add explanations for a failure mode in logging (#324) * Add explanations for a failure mode in logging Thanks @abuisine for reporting that one too! * Typo --- slides/kube/logs-centralized.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/slides/kube/logs-centralized.md b/slides/kube/logs-centralized.md index d316b2fa..a707e0b9 100644 --- a/slides/kube/logs-centralized.md +++ b/slides/kube/logs-centralized.md @@ -113,7 +113,7 @@ and a few roles and role bindings (to give fluentd the required permissions). - The first time you connect to Kibana, you must "configure an index pattern" -- Just use the one that is suggested, `@timestamp` +- Just use the one that is suggested, `@timestamp`.red[*] - Then click "Discover" (in the top-left corner) @@ -123,6 +123,9 @@ and a few roles and role bindings (to give fluentd the required permissions). `kubernetes.host`, `kubernetes.pod_name`, `stream`, `log` +.red[*]If you don't see `@timestamp`, it's probably because no logs exist yet. +
Wait a bit, and double-check the logging pipeline! + --- ## Caveat emptor