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
This commit is contained in:
Jérôme Petazzoni
2018-08-15 04:04:18 -05:00
committed by GitHub
parent 6b662d3e4c
commit dc98fa21a9

View File

@@ -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.
<br/>Wait a bit, and double-check the logging pipeline!
---
## Caveat emptor