Planning central logging
Conceptually, central logging is very simple. On each node, you run a dedicated agent that intercepts all log messages from all the pods and containers on the node, and sends them, along with enough metadata, to a central repository where they are stored safely.
As usual, if you run on the Google platform, then GKE's got you covered, and there is a Google central-logging service integrated nicely. For other platforms, a popular solution is fluentd, Elasticsearch, and Kibana. There is an official add-on to set up the proper services for each component. The fluentd-elasticsearch add-on is at http://bit.ly/2f6MF5b.
It is installed as a set of services for Elasticsearch and Kibana, and the fluentd agent is installed on ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access