Wondering how to set up debug logging for AWS DMS task? We can help you!

Here at Bobcares, we often handle requests to set up debug logging for our customers as a part of our Server Management Services.

Today let’s see how our Support Engineers do this for our customers.

How to set up debug logging for AWS DMS task

The steps that our Support Engineers follow to do this set up is given below:

Enable debugging for an AWS DMS task

To monitor the AWS DMS task, we can modify the logging task settings and specify which component activities and severity values are logged.

The following example uses the most detailed level of debug logging:

LOGGER_SEVERITY_DETAILED_DEBUG.

Generally, detailed debug logging requires a large amount of storage space. However, we can use ongoing replication, also known as change data capture (CDC) so that the log entries consume less storage space.

1.  First open the AWS DMS console, and go to Database migration tasks.

2. Then select the task.

3. Further from the Overview details section, click on Task Settings (JSON) section.

4. After that copy and paste the Logging section of task settings into a JSON editor.

5. Now edit the Severity setting of each log component that we wish to enable detailed debug logging on by replacing LOGGER_SEVERITY_DEFAULT with LOGGER_SEVERITY_DETAILED_DEBUG.

Example

{
    "Logging": {
        "EnableLogging": true,
        "LogComponents": [{
                "Id": "SOURCE_UNLOAD",
                "Severity": "LOGGER_SEVERITY_DEFAULT"
            },
            {
                "Id": "TARGET_LOAD",
                "Severity": "LOGGER_SEVERITY_DEBUG"
            },
            {
                "Id": "SOURCE_CAPTURE",
                "Severity": "LOGGER_SEVERITY_DEFAULT"
            },
            {
                "Id": "TARGET_APPLY",
                "Severity": "LOGGER_SEVERITY_DETAILED_DEBUG"
            },
            {
                "Id": "TASK_MANAGER",
                "Severity": "LOGGER_SEVERITY_DEFAULT"
            }
        ],
        "CloudWatchLogGroup": "dms-tasks-xxxx",
        "CloudWatchLogStream": "dms-task-xxxxx"
    }
}

5. Then save the JSON file, and note the Task ARN and file path for use later.

6. After that install and configure the latest version of the AWS CLI.

7. Now, run the modify-replication-task AWS CLI command, using the Task ARN and the path of the file that was saved earlier.

Linux example

aws dms modify-replication-task --replication-task-arn arn:aws:dms:us-east-1:123456789012:task:2PVREMWNPGYJCVU2IBPTOYTIV4 --replication-task-settings file://your-task-settings.json

Windows example

aws dms modify-replication-task --replication-task-arn arn:aws:dms:us-east-1:123456789012:task:2PVREMWNPGYJCVU2IBPTOYTIV4 --replication-task-settings file://"c:\temp\your-task-settings.json"

8. And open the AWS DMS console, select Database migration tasks.

9. Then confirm that the task status is Modifying.

10. From the Overview details section for the task, under Task Settings, confirm that the Severity setting is LOGGER_SEVERITY_DETAILED_DEBUG for each log component that we modified.

The next time that we run this task, we will get detailed debug logs.

Modify an existing task to enable debugging

We can also modify an existing task to enable detail debugging.

1. Firstly modify the AWS DMS task.

2. Then confirm that the Enable CloudWatch logs checkbox is selected.

3. Finally, change the Severity of the five standard loggers in the drop-down list, as required.

[Need assistance? We can help you]

Conclusion

To conclude, we saw the steps that our Support Techs follow to set up debug logging for AWS DMS task.