I walked you through the hard way of deploying an ELK stack using packages. This can be error prone and really doesn’t ring well with current DevOps/Infrastructure as Code mantra. So this post will help you accomplish the same setup but using Puppet for configuration management.
Jenkins has great console logging but if you have a ton of jobs because you’re using microservices then keeping track of all these logs can be quite a chore. In addition, you might want to analyze these logs to identify cascading failures or environment issues that is causing your continuous delivery pipeline to fail. This post will cover how to setup an Elasticsearch and Kibana server that is a powerful option to analyze and combine your logs into a “single pane of glass” dashboard.