Search <book_title>...

Veritas CloudPoint Administrator's Guide

Last Published: 2020-06-04

Product(s): CloudPoint (2.2.2)

Platform: Linux

About the CloudPoint fluentd configuration file

Fluentd uses a configuration file that defines the source of the log messages, the set of rules and filters to use for selecting the logs, and the target destinations for delivering those log messages.

The fluentd daemon running on the CloudPoint host is responsible for sending the CloudPoint logs to various destinations. These target destinations, along with the other details such as input data sources and required fluentd parameters are defined in the plugin configuration file. For CloudPoint, these plugin configurations are stored in a fluentd configuration file that is located at /cloudpoint/fluent/fluent.conf on the CloudPoint host. The fluentd daemon reads the output plugin definition from this configuration file to determine where to send the CloudPoint log messages.

The following output plugin definitions are added to the configuration file by default:

CloudPoint MongoDB collection (Fluentd::logs)

This represents the default MongoDB collection that stores all the CloudPoint service logs on the CloudPoint host.

The plugin is defined as follows:

# Send to a mongodb collection fluentd:logs
<store>
@type mongo
host flexsnap-mongodb
port 27017
database fluentd
collection logs

ssl true
ssl_cert /cloudpoint/keys/mongodb.pem
ssl_key /cloudpoint/keys/mongodb.pem
ssl_ca_cert /cloudpoint/keys/cacert.pem

capped
capped_size 5120m
</store>

STDOUT
This is used to send the CloudPoint log messages to the flexsnap-fluentd service container logs. These logs can be obtained using standard Docker commands.
The plugin is defined as follows:
```
# Send to fluentd docker logs
<store>
@type stdout
</store>
```

Additionally, the CloudPoint fluentd configuration file includes plugin definitions for the following destinations:

Splunk
ElasticSearch

These plugin definitions are provided as a template and are commented out in the file. To configure an actual Splunk or ElasticSearch target, you can uncomment these definitions and replace the parameter values as required.