Amazon MSK Replicator now supports log forwarding for replication visibility

Amazon MSK Replicator Updates

Amazon MSK Replicator now delivers replicator logs to provide end-to-end visibility into replication health. These logs surface critical replication events and errors along with guidance on how to resolve each issue, enabling faster troubleshooting without requiring AWS Support.

MSK Replicator automates data replication between Kafka clusters, eliminating the need to manage custom replication infrastructure or configure open-source tools. With this update, you can track replication progress and diagnose issues with actionable log entries that surface common replication errors, including insufficient permissions on source topics, partition quota exhaustion on target clusters, and records exceeding size limits.

You can enable log delivery when creating or updating a Replicator using the Amazon MSK console, AWS CLI, or AWS CloudFormation, and forward logs to Amazon CloudWatch, Amazon S3, or Amazon Data Firehose.

What to do

• Enable log delivery for your MSK Replicator.
• Forward logs to your preferred destination: Amazon CloudWatch, Amazon S3, or Amazon Data Firehose.
• Review replicator logs for critical replication events and errors.
• Follow the prescriptive guidance provided to resolve issues.

Source: AWS release notes

If you need further guidance on AWS, our experts are available at AWS@westloop.io. You may also reach us by submitting the Contact Us form.