Precisely replication publishes metrics and logs to CloudWatch enabling organizations to use it to monitor their data replication pipelines health and key events.
The sqdservice process reports usage metering into the AWS Marketplace at the top of each hour in the form of total megabytes sent to replication targets by Apply engines. It publishes log events into CloudWatch that provide the usage, in bytes, contributed by each replication engine and the total in megabytes along with whether AWS Marketplace accepted the report or not.
A sqdcloudwatch process is started by default to publish metrics on behalf of replication engines that are running in the AMI. See Precisely Replication Metrics for a detailed list of the metrics that are published. It also publishes log events for started Apply engine stdout and stderr files into corresponding CloudWatch streams. If it gets stopped for any reason, you will have to manually start it. You will also need to stop/start it manually if you want to change the reporting interval from the default 60 seconds to any other number of seconds as shown below.
connect> nohup sqdcloudwatch –-metrics_interval=300 &
connect> nohup sqdcloudwatch –-log_interval=300 &
You can also manually start a sqdcloudwatch process to monitor activity on a remote replication system such as where the replication capture agent is running by specifying the host and port of the remote sqdaemon process.
connect> nohup sqdcloudwatch --host=ip-172-31-3-141.us-west-1.compute.internal –port=2626 &