2 Concepts, architecture, and deployment of Fluentd

Chapter 1 looked at the theory, industry trends, and use cases that Fluentd can help us with. This chapter discusses how Fluentd works, including deploying and running the simplest of configurations to implement the traditional developer’s “Hello World.”

2.1 Architecture and core concepts

When you’re driving a car, it is a lot easier when you have some basic appreciation of how the vehicle is powered (e.g., gas, diesel, electric, liquefied petroleum gas). The mental models that come with such understanding mean we can learn what to expect—whether we can expect to hear the engine rev, whether it’s possible for the engine to stall, and how the gears work (if there are any). For the same reason, before we start working with Fluentd and Fluent Bit, it is worth investing time in understanding how these tools work. Based on this, we should run through some of the building blocks of Fluentd that will help with the mental models.

2.1.1 The makeup of a log event

2.1.2 Handling time

2.1.3 Architecture of Fluentd

2.1.4 Fluent configuration execution order

2.1.5 Directives

2.1.6 Putting timing requirements into action

2.2 Deployment of Fluentd

2.2.1 Deploying Fluentd for the book’s examples

2.2.2 Deployment considerations for Fluentd

2.2.3 Fluentd minimum footprint

2.2.4 Simple deployment of Ruby

2.2.5 Simple deployment of Fluentd

2.2.6 Deploying a log generator

2.2.7 Installing Postman