Help Center/ Elastic Load Balance/ Best Practices/ Security/ Querying ELB Operation Records on the CTS Console

Updated on 2025-11-14 GMT+08:00

View PDF

Querying ELB Operation Records on the CTS Console

Scenarios

Cloud Trace Service (CTS) records operations performed on cloud service resources. A record contains information such as the user who performed the operation, IP address, operation content, and returned response message. These operation records let you do security audit, trace issues, and locate resources quickly. They also help you plan and use resources, and identify high-risk or non-compliant operations.

After CTS is enabled, it can record ELB operations. This section describes the fields in CTS records.

What Is a Trace?

A trace is an operation log for a cloud service resource, tracked and stored by CTS. Traces record operations such as adding, modifying, or deleting cloud service resources. You can view them to identify who performed operations and when for detailed tracking.

What Is a Management Tracker and Data Tracker?

A management tracker identifies and associates with all your cloud services, recording all user operations. It records management traces, which are operations performed by users on cloud service resources, such as their creation, modification, and deletion.

A data tracker records details of user operations on data in OBS buckets. It records data traces reported by OBS, detailing user operations on data in OBS buckets, including uploads and downloads.

Viewing the Trace for Creating a Load Balancer in the Trace List of the New Edition

Create a dedicated load balancer.
Log in to the CTS console.
In the navigation pane, choose Trace List.
In the time range drop-down list above the trace list, select a desired query time range: Last 1 hour, Last 1 day, or Last 1 week. You can also select Custom to specify a time range within the last seven days.

The search box above the trace list supports advanced queries. Combine one or more filters to refine your search. In this practice, select Cloud service: ELB.

**Table 1** Trace filtering parameters
Parameter	Description
Cloud service	Abbreviation of the cloud service name. In this practice, select Cloud service: ELB. The entered value is case-sensitive and requires an exact match. Fuzzy matching is not supported.

Figure 1 Filtering ELB traces

On the trace list page, you can view the traces of the load balancer created in step 1.
Click the trace name to view its details.
Figure 2 ELB trace details
On the Trace List page, export operation records, refresh the trace list, and specify columns to display.
1. Enter any keyword in the search box and press Enter to filter desired traces.
2. Click Export to export all traces in the query result as an .xlsx file. The file can contain up to 5,000 records.
3. Click to view the latest information about traces.
4. Click to define the information to be displayed in the trace list. If Auto wrapping is enabled (), excess text will be moved down to the next line; otherwise, the text will be truncated. By default, this function is disabled.
(Optional) On the Trace List page of the new edition, click Old Edition in the upper right corner to switch to the Trace List page of the old edition.

CTS Record Fields

**Table 2** CTS record fields
Field	Description
request	Request body content. In this practice, this field indicates the request body for calling the API to create a load balancer.
trace_id	ID of the trace recorded by CTS.
code	HTTP status code returned by the associated API.
trace_name	Trace name.
resource_type	Type of the resource. In this practice, the resource type is loadbalancer.
trace_rating	Trace severity. If the load balancer is created successfully, trace_rating is normal. Value options: normal: The operation succeeded. warning: The operation failed. incident: The operation caused a serious consequence, for example, a node failure or service interruption.
message	Remarks added by ELB to a trace.
source_ip	Source IP address of the request.
domain_id	Domain ID.
trace_type	Trace source. The value can be ApiCall, ConsoleAction, or SystemAction.
service_type	Type of the cloud service whose traces are to be queried. service_type of ELB is ELB.
event_type	Event type.
project_id	Project ID.
read_only	Whether the request is read-only. read_only is false for adding, deleting, or modifying resources, and true for querying resources.
resource_id	ID of the resource whose traces are to be queried.
tracker_name	Name of the tracker. If trace_type is system, this field defaults to system. If trace_type is data, this field indicates the name of the data tracker.
operation_id	Operation ID of the trace.
resource_account_id	ID of the account to which the resource belongs.
time	Time when the trace was generated.
resource_name	Resource name.
user	Information about the user who performs operations on the resource.
record_time	Time when a trace was recorded by CTS.
user_agent	ID of the client agent that sends the request.
api_version	API version.
response	Response body.
request_id	Request ID of the current request, which can be used to locate faults for ELB.