- About DM
- DM Overview
- DM 5.3 Release Notes
- Basic Features
- Advanced Features
- Merge and Migrate Data from Sharded Tables
- Migrate from MySQL Databases that Use GH-ost/PT-osc
- Filter Certain Row Changes Using SQL Expressions
- DM Architecture
- Benchmarks
- Quick Start
- Deploy
- Maintain
- Tools
- Cluster Upgrade
- Manage Data Source
- Manage a Data Migration Task
- Manually Handle Sharding DDL Lock
- Manage Schemas of Tables to be Migrated
- Handle Alerts
- Daily Check
- Usage Scenarios
- Troubleshoot
- Performance Tuning
- Reference
- Secure
- FAQ
- Glossary
- Release Notes
Daily Check
This document summarizes how to perform a daily check on TiDB Data Migration (DM).
Method 1: Execute the
query-statuscommand to check the running status of the task and the error output (if any). For details, see Query Status.Method 2: If Prometheus and Grafana are correctly deployed when you deploy the DM cluster using TiUP, you can view DM monitoring metrics in Grafana. For example, suppose that the Grafana's address is
172.16.10.71, go to http://172.16.10.71:3000, enter the Grafana dashboard, and select the DM Dashboard to check monitoring metrics of DM. For more information of these metrics, see DM Monitoring Metrics.Method 3: Check the running status of DM and the error (if any) using the log file.
- DM-master log directory: It is specified by the
--log-fileDM-master process parameter. If DM is deployed using TiUP, the log directory is{log_dir}in the DM-master node. - DM-worker log directory: It is specified by the
--log-fileDM-worker process parameter. If DM is deployed using TiUP, the log directory is{log_dir}in the DM-worker node.
- DM-master log directory: It is specified by the
What’s on this page
Was this page helpful?