CloudTable uses CTS to record operations associated with CloudTable for later query, audit, and backtrack operations.
The following key operation traces of CloudTable are recorded in audit logs. For details, see Table 1.
Operation | Trace Name | Resource Type |
|---|---|---|
Creating a cluster | createCloudTableClusterV3 | cluster |
Scaling out a node | growCloudTableCluster | cluster |
Restarting a cluster | rebootCloudTableCluster | cluster |
Setting the storage quota | storageClusterAction | cluster |
Modifying a feature | modifyClusterFeatures | cluster |
Configuring parameters | modifyClusterSetting | cluster |
Binding a role to a user in Doris | addAccountRole | cluster |
Binding a user to a tenant in Doris | bindAccountWithTenant | cluster |
Enumerating database information | copierListDatabaseInfo | cluster |
Enumerating cluster node information | copierListNodeInfo | cluster |
Creating a catalog in Doris | createCatalogV3 | cluster |
Creating a Doris user | createCloudTableAccount | cluster |
Creating a role | createRole | cluster |
Creating a tenant | createTenante | cluster |
Testing the function of creating a catalog in Doris | createTestCatalogV3 | cluster |
Deleting a catalog connection in Doris | deleteCatalogV3 | cluster |
Deleting a cluster | deleteCloudTableClusterV2 | cluster |
Deleting a role | deleteRole | cluster |
Disabling cluster logs | disableLTSAccess | cluster |
Enabling cluster logs | enableLTSAccess | cluster |
Obtaining catalogs in Doris | getCatalogs | cluster |
Obtaining cluster information | getClusterInfo | cluster |
Obtaining database information | getDatabases | cluster |
Obtaining role information | getRoles | cluster |
Obtaining table information | getTables | cluster |
Accessing the disk expansion page | growCloudTableDisk | cluster |
Expanding specifications | growCloudTableFlavor | cluster |
Modifying Doris configuration parameters | modifyClusterSettingV3 | cluster |
Modifying role permissions in Doris | modifyRolePermission | cluster |
Restarting a node | restartInstance | cluster |
Modifying a tenant in Doris | updateTenant | cluster |
Restart | REBOOTING | cluster |
Capacity expansion | GROWING | cluster |
Deletion | DELETING | cluster |
Creating a tenant | createTenant | cluster |
Deleting a tenant in Doris | deleteTenant | cluster |
Scanning and killing SQL statements | killQueryBySqlId | cluster |
Deleting a Doris user | deleteCloudTableAccount | cluster |
Updating a Doris user | updateCloudTableAccount | cluster |
A tracker will be automatically created after CTS is enabled. All traces recorded by CTS are associated with a tracker. Currently, only one tracker can be created for each account.
If you are a first-time CTS user and do not have any created tackers in the tracker list, enable CTS first. For details, see Getting Started > Overview in the Cloud Trace Service User Guide.
If you have enabled CTS, the system has automatically created a management tracker. Only one management tracker can be created and it cannot be deleted. You can also manually create a data tracker. For details, see Management Trackers > Creating a Tracker in the Cloud Trace Service User Guide.
If you want to disable the audit log function, disable the tracker in CTS.
For details about how to enable or disable a tracker, see Management Trackers > Disabling or Enabling a Tracker in the Cloud Trace Service Getting Started.
The following four filter criteria are available:
on the left of the trace to be queried to extend its details.Figure 1 Trace

Figure 2 Viewing a trace

For details about key fields in the CTS trace structure, see the "Trace References" > "Trace Structure" in the Cloud Trace Service User Guide.