This topic describes the observability feature provided by custom ApsaraMQ for Kafka connectors. This topic also describes how to troubleshoot issues.
Observability
Custom ApsaraMQ for Kafka connectors provide the observability feature. You can use this feature to monitor metrics that are related to ApsaraMQ for Kafka instances, workers, and connectors.
Log on to the ApsaraMQ for Kafka console. In the Resource Distribution section of the Overview page, select the region where the ApsaraMQ for Kafka instance that you want to manage resides.
In the left-side navigation pane, choose .
On the Tasks page, find the ApsaraMQ for Kafka connector that you want to manage and click Details in the Actions column.
In the left-side navigation tree, click Metric Monitoring.
Click the ApsaraMQ for Kafka Instance Monitoring tab to view the monitoring data of each ApsaraMQ for Kafka instance.
Click the ApsaraMQ for Kafka Topic Monitoring tab to view the monitoring data of each topic.
Click the Worker Monitoring tab to view the resource consumption of each Serverless App Engine (SAE) application and instance. Kafka Connect workers run on SAE. The resource consumption of an SAE application or instance reflects the resource usage of the connector.
Click the Connector Monitoring tab to view the running status of Kafka Connect tasks. The connector monitoring metric is provided by Kafka Connect. When a task fails to run, you can view the detailed information about the issue on this page. This helps you troubleshoot the issue.
Troubleshooting
If an ApsaraMQ for Kafka connector fails to run, you can perform the following steps to troubleshoot the issue:
In the left-side navigation tree of the task details page, click Overview.
In the Basic Information section, click Running Exception to view the error type and error details.
If the issue occurs because a Kafka Connect task fails to run, you can click Diagnostics to go to the Connector Monitoring page to view the detailed information about the failed task.
If you still cannot resolve the issue after you perform the preceding steps, you can log on to the SAE console for further debugging.
In the left-side navigation tree of the task details page, click Overview.
In the Worker Information section, click the instance name next to SAE Application to go to the application details page in the SAE console.
On the Basic Information page, click the Instance Deployment Information tab.
In the Action column of the corresponding instance, click Webshell to log on to the running environment of Kafka Connect.
You can view the running logs of the connector in the /opt/kafka/logs/connect.log file to troubleshoot the issue.