{"id":2023,"date":"2019-07-18T03:58:42","date_gmt":"2019-07-18T10:58:42","guid":{"rendered":"https:\/\/hometechhacker.com\/?p=2023"},"modified":"2020-10-26T09:50:36","modified_gmt":"2020-10-26T16:50:36","slug":"centralizing-docker-logging-using-logspout-and-graylog","status":"publish","type":"post","link":"https:\/\/hometechhacker.com\/centralizing-docker-logging-using-logspout-and-graylog\/","title":{"rendered":"Centralizing Docker Logging Using Logspout and Graylog"},"content":{"rendered":"
<\/div>\n
\"Logspout,<\/figure>\n\n\n\n

I’m a big fan of Docker<\/a> and of centralizing logs<\/a>. Recently, as I’ve moved more and more of my applications to containers, I’ve realized I’m not centralizing as many of my logs to Graylog<\/a>. I’m used to applications logging to syslog and then aggregating the syslogs of each machine.<\/p>\n\n\n\n

However, Docker doesn’t work this way. Docker uses logging drivers to send their logs in various formats to various applications. After looking into this I decided a combination of Logspout and Graylog was the best way to get the kind of logging I want with the least downsides.<\/p>\n\n\n\n

\n

Table of Contents<\/p>\n