Updated on 2024-12-24 GMT+08:00
Cluster Log Management
Cluster logs are collected and sent to Log Tank Service (LTS). You can check or dump the collected cluster logs on LTS.
Currently, the following log types are supported:
- Path for storing HBase cluster logs: /var/chroot/cloudtable/hbase/logs/
- hbase-Ruby-master-$hostname.log
- hbase-Ruby-regionserver-$hostname.log
- hbase-audit.log
- Path for storing ClickHouse cluster logs: /var/log/clickhouse/
- clickhouse-server.log
- clickhouse-server.err.log
Enabling LTS
- Log in to the CloudTable console.
- Click in the upper left corner to select a region.
- Click Clusters. The cluster list is displayed.
- In the cluster list, click a cluster name to go to the cluster details page. In the navigation pane on the left, click Logs. The Logs page is displayed.
- Click in the upper left corner of the page to enable LTS.
- If this function is enabled for the first time, the Create Agency dialog box is displayed. Click OK to authorize the agency.
- If LTS has been enabled and authorized to create an agency, no authorization is required when LTS is enabled again.
Checking Cluster Logs
- Log in to the CloudTable console.
- Click in the upper left corner to select a region.
- Click Clusters. The cluster list is displayed.
- In the cluster list, click a cluster name to go to the cluster details page. In the navigation pane on the left, click Logs. The Logs page is displayed.
- Select View Logs in the Operation column. The LTS console is displayed.
Disable Logging
- Log in to the CloudTable console.
- Click in the upper left corner to select a region.
- Click Clusters. The cluster list is displayed.
- In the cluster list, click a cluster name to go to the cluster details page. In the navigation pane on the left, click Logs. The Logs page is displayed.
- Toggle off the LTS switch.
- Click OK in the dialog box.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot