3 Capturing inputs

 

This chapter covers

  • Reading log events from files
  • Capturing console logging
  • Ingesting OpenTelemetry data
  • Integrating with logging frameworks

This chapter is all about capturing metrics, traces, and (most important) logs using Fluent Bit and a variety of plugins that support the latest techniques in the form of OpenTelemetry, as well as the established practices of using stdout and log files. We’ll focus on logs, as Fluent Bit originated from log handling. Logs also offer the most flexible signals and can be easily used to provide data that embodies metrics and traces; we’ll touch on techniques that allow us to change a signal’s type. We’ll come back to this subject in other chapters, including chapter 9.

3.1 Fluent Bit plugins

Fluent Bit has a respectable portfolio of plugins. To understand the relationships between the parts of Fluent Bit, let’s see how the inputs fit into the overall logical architecture, shown in figure 3.1.

Figure 3.1 Logical architecture of Fluent Bit, with this chapter's focus highlighted
figure

3.2 OS and device sources

3.2.1 Monitoring infrastructure with native executables

3.2.2 Tuning monitoring sources

3.2.3 Device sources

3.3 Using stdout

3.3.1 The twelve-factor app and Fluent Bit

3.3.2 Running the containerized Log Simulator

3.4 File-based log events

3.5 Capturing log files

3.5.1 Simple file consumption

3.5.2 Supporting long-running processes

3.5.3 Capturing logs from short-lived applications

3.6 Network events and communication between Fluent Bit and Fluentd

3.6.1 Network input sources

3.6.2 HTTP source

3.6.3 Securing communication with SSL/TLS

3.6.4 forward source

sitemap