This article details all the steps needed to build a centralized logging architecture on Linux systems. If you are a Linux system administrator, you probably spend a lot of time browsing your log files in order to find relevant information about past events. Most of the time, you are not working with a single machine, but with many different Linux machines, each having its own local log storage. Now if you were to browse logs for many different machines, you would have to individually connect to every single one of them, locate logs and try to find the information that you are looking for. This is of course in the case where you can physically access the machine, presupposing that the machine is up and that you are not denied the access to it.



Read more

join Faun to receive similar hand-curated and must-read articles and news.

Related Posts


Brendan Gregg , 2 months ago

BPF Performance Tools: Linux System And Application Observability (Book)

BPF (eBPF) tracing is a superpower that can analyze everything, and I'll show you how in my upcoming..

2 months, 3 weeks ago

Saschagrunert/Demystifying-containers

A series of blog posts and talks about the world of containers 📦..

1 month ago

16 Essentials For Sysadmin Superheroes

You know you're a sysadmin if you are either knee-deep in system logs, constantly handling user erro..

4 weeks, 1 day ago

Muesli/Scratchy

Quickly Bootstrap a Linux Distro in a (Non-docker) Container And Interactively Execute Something in ..