Book Image

The Software Developer's Guide to Linux

By : David Cohen, Christian Sturm
5 (2)
Book Image

The Software Developer's Guide to Linux

5 (2)
By: David Cohen, Christian Sturm

Overview of this book

Developers are always looking to raise their game to the next level, yet most are completely lost when it comes to the Linux command line. This book is the bridge that will take you to the next level in your software development career. Most of the skills in the book can be immediately put to work to make you a more efficient developer. It’s written specifically for software engineers, not Linux system administrators, so each chapter will equip you with just enough theory to understand what you’re doing before diving into practical commands that you can use in your day-to-day work as a software developer. As you work through the book, you’ll quickly absorb the basics of how Linux works while you get comfortable moving around the command line. Once you’ve got the core skills, you’ll see how to apply them in different contexts that you’ll come across as a software developer: building and working with Docker images, automating boring build tasks with shell scripts, and troubleshooting issues in production environments. By the end of the book, you’ll be able to use Linux and the command line comfortably and apply your newfound skills in your day-to-day work to save time, troubleshoot issues, and be the command-line wizard that your team turns to.
Table of Contents (20 chapters)
18
Other Books You May Enjoy
19
Index

Centralized logging

In a corporate setting, it is typical to centralize logs. This makes it easier to connect the dots when debugging issues. It also means that in a distributed application, not every log on each physical or virtual machine or container has to be looked at individually. These centralized logging services typically make it easy and fast to query large amounts of logs, especially when the company uses structured logging and services adhere to a uniform log structure.

These logging services are either their own products, such as rsyslog, Loki, the ELK stack (Elastic Search, Logstash, and Kibana), and Graylog, or they are managed services. These can, for example, be the hosted variants of the services we just mentioned or cloud-specific logging solutions, such as Google’s operations suite (formerly known as Stackdriver), AWS CloudWatch, or Azure Monitor. There are many similarities between these systems in that they provide mechanisms to “ship”...