td-agent package.td-agenttd-agent instance will be up and running with a predefined template configuration file.td-agent using systemctl command:td-agent writes its operation logs to the following file:calyptia-fluentdcalyptia-fluentd instance will be up and running with a predefined template configuration file.calyptia-fluentd using systemctl command:calyptia-fluentd writes its operation logs to the following file:in_kafka. In the same way, if it publishes data and connects to MongoDB, it is called out_mongo.in_forward plugin as an input source and out_file plugin as an output endpoint:td-agenttd-agent-gem is used to manage plugin gems. For example, the following command installs a plugin to connect to S3 (including both in_s3 and out_s3 plugins):calyptia-fluentdcalyptia-fluentd-gem is used to manage plugin gems. For example, the following command installs a plugin to connect to S3 (including both in_s3 and out_s3 plugins):td-agent so you do not need to install them manually.<source>. Each block contains a set of options for a specific data endpoint.<source> block and set up its settings like this:@type parameter specifies which plugin to use. Note that the plugin type prefix i.e. in_, out_, etc. is not needed here. In this example, the input plugin is specified as syslog, not in_syslog.<match> block. Syntactically, <match> is slightly different from <source> in the sense that it requires a filter expression as an argument.debug.log, you need to mention this tag as an argument in <match> like this:* can be used in the filter expression. For example, debug.* matches debug.log, debug.foo, etc.**. For example, debug.** matches not only debug.log, but also debug.log.bar or debug.log.level.critical, etc.