There is a point to this story, but it has temporarily escaped my mind...
Contact Me MyFaceBook MyLinkedIn MyGitHub MyTwitter

Set-up a Centralized Logging Solution

Centralized logging can be very useful when attempting to identify problems with servers or applications, as it allows you to search through all of your logs in a single place. It is also useful because it allows you to identify issues that span multiple servers by correlating their logs during a specific time frame.

This solution uses the ELK stack, which has three main components:

  • Elasticsearch: Stores all of the logs
  • Logstash: The server component of Logstash that processes incoming logs
  • Kibana: Web interface for searching and visualizing logs, which will be proxied through Nginx

On the Servers that I want to combine the logs for I install the following:

  • Filebeat: Offers a lightweight way to forward and centralize logs and files.
  • Metricbeat: Collect metrics from your systems and services.
  • Packetbeat: Network packet analyzer that sends data to Logstash.
  • Winlogbeat: Streams Windows event logs to Logstash.
Copyright © 2019 by Julian Easterling. SOME RIGHTS RESERVED.
Privacy Policy              Terms of Use             


Creative Commons License
Except where otherwise noted, content on this site is
licensed under a Creative Common Attribution-Share Alike 4.0 International License.


All of the opinions expressed on this website are those of Julian Easterling and
do not represent the views of any of my current and previous clients or employers in any way.

If you notice an error on the site or content that has not been properly attributed, bring
it to my attention using the contact page and I will endeavor to fix it as soon as I can.

I accept no responsibility or liability for any damages incurred by following any of
my advice or by using any of the information on my site or of those sites that I link to.