Fluentd and Multiple Instances

45 minutes
  • 3 Learning Objectives

About this Hands-on Lab

In this lab, you will be provided with a single server with fluentd preinstalled for you. Your task is to create a configuration file that reads the `/var/log/messages` log and sends it to two Fluentd instances. You will set the targets to be a primary and a standby. You will then create two separate Fluentd instances that listen for the incoming log events that are being sent and display them to the stdout. It must be designed so that, when the primary target goes down, the traffic is sent to the standby instance.

Learning Objectives

Successfully complete this lab by achieving the following learning objectives:

Create source1.conf with Active and Standby Log Forwarding

On the provided server, create a configuration called source1.conf. This configuration will send the /var/log/messages logs to two Fluentd instances on the same server using the forward plugin. The targets will use and either port 24225 or port 24226 with an active and standby configuration.

Configure a target1 and target2 Instance to Receive Logs from the source1 Instance

Configure Fluentd target1 instance and a target2 instance so they will receive logs from the source1 instance. The configuration files should be called target1.conf and target2.conf and should use different ports on localhost. The target1 instance should use port 24225. The target2 instance should use port 24226

Test Logs Are Received

Test that the changes have worked and any new entries to the /var/log/messages on source1 are now being sent to the td-agent stdout on target1. If target1 instance is stopped, then logs should go to the target2 instance.

The logger command can be used to send a message to /var/log/messages.

Additional Resources

You have been told that with Fluentd, you can have a configuration that is redundant. So if an instance goes down, traffic can be automatically sent to a standby instance.

You will create a configuration file that reads the /var/log/messages log, tags the traffic, and uses a plugin to send that traffic to a primary and a standby Fluentd instance.

You will then create two different Fluentd configurations to support a primary and a standby Fluentd instance. These instances will accept traffic from other Fluentd instances and send those events to stdout.

To save resources, you will be doing this on a single server. This is for testing purposed to show it can be done.

You will set the targets to listen on localhost and on different ports. This allows all three Fluentd instances to run on the same server.

What are Hands-on Labs

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.

Sign In
Welcome Back!

Psst…this one if you’ve been moved to ACG!

Get Started
Who’s going to be learning?