Veritas CloudPoint Administrator's Guide
- Getting started with CloudPoint
- Section I. Installing and configuring CloudPoint
- Preparing for installation
- Deploying CloudPoint
- Deploying CloudPoint in the AWS cloud
- Using plug-ins to discover assets
- Configuring off-host plug-ins
- AWS plug-in configuration notes
- Google Cloud Platform plug-in configuration notes
- Microsoft Azure plug-in configuration notes
- HPE RMC plug-in configuration notes
- NetApp plug-in configuration notes
- Hitachi plug-in configuration notes
- InfiniBox plug-in configuration notes
- About CloudPoint plug-ins and assets discovery
- Configuring the on-host agents and plug-ins
- Oracle plug-in configuration notes
- Protecting assets with CloudPoint's agentless feature
- Preparing for installation
- Section II. Configuring users
- Section III. Protecting and managing data
- User interface basics
- Indexing and classifying your assets
- Protecting your assets with policies
- Tag-based asset protection
- Replicating snapshots for added protection
- Managing your assets
- About snapshot restore
- Single file restore requirements and limitations
- Additional steps required after a SQL Server snapshot restore
- Monitoring activities with notifications and the job log
- Protection and disaster recovery
- Section IV. Maintaining CloudPoint
- CloudPoint logging
- Troubleshooting CloudPoint
- Working with your CloudPoint license
- Managing CloudPoint agents and plug-ins
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Section V. Reference
How fluentd-based CloudPoint logging works
When you install CloudPoint, or upgrade to release 2.2, the following changes occur on the CloudPoint host:
A new container service named
flexsnap-fluentd
is started on the CloudPoint host. This service is started before all the other CloudPoint container services. Theflexsnap-fluentd
service serves as thefluentd
daemon on the host.All the CloudPoint container services are then started with
fluentd
as the Docker logging driver.A
fluentd
configuration file is created at/cloudpoint/fluent/fluent.conf
.This file contains the output plugin definitions that are used to determine where the CloudPoint logs are redirected for consumption.
Once all the infrastructure components are ready, each of the CloudPoint services begin to send their respective log messages to the configured Docker fluentd
logging driver. The fluentd
daemon then redirects the structured logs to the output plugins configured in the fluentd
configuration file. These logs are sent to the CloudPoint MongoDB collection as per the default settings in the fluent.conf
configuration file. All the log messages are stored in a JSON format.