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

Viewing Cloud Eye Logs

Scenarios

After CTS is enabled, CTS starts recording operations on cloud resources. The CTS management console stores the operation records of the last 7 days.

This section describes how to query or export the last seven days of operation records on the CTS console.

  1. Log in to the CTS console.
  2. In the navigation pane, choose Trace List.
  3. 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 custom time range within the last seven days.
  4. The search box above the trace list supports advanced queries. Combine one or more filters to refine your search.

    Table 1 Trace filtering parameters

    Parameter

    Description

    Trace Name

    Name of a trace.

    The entered value is case-sensitive and requires an exact match. Fuzzy matching is not supported.

    For details about the operations that can be audited for each cloud service, see Supported Services and Operations.

    Example: updateAlarm

    Trace Source

    Cloud service name abbreviation.

    The entered value is case-sensitive and requires an exact match. Fuzzy matching is not supported.

    Example: IAM

    Resource Name

    Name of a cloud resource involved in a trace.

    The entered value is case-sensitive and requires an exact match. Fuzzy matching is not supported.

    If the cloud resource involved in the trace does not have a resource name or the corresponding API operation does not involve the resource name parameter, leave this field empty.

    Example: ecs-name

    Resource ID

    ID of a cloud resource involved in a trace.

    The entered value is case-sensitive and requires an exact match. Fuzzy matching is not supported.

    Leave this field empty if the resource has no resource ID or if resource creation failed.

    Example: {VM ID}

    Trace ID

    Value of the trace_id parameter for a trace reported to CTS.

    The entered value requires an exact match. Fuzzy matching is not supported.

    Example: 01d18a1b-56ee-11f0-ac81-******1e229

    Resource Type

    Type of a resource involved in a trace.

    The entered value is case-sensitive and requires an exact match. Fuzzy matching is not supported.

    For details about the resource types of each cloud service, see Supported Services and Operations.

    Example: user

    Operator

    User who triggers a trace.

    Select one or more operators from the drop-down list.

    If the value of trace_type in a trace is SystemAction, the operation is triggered by the service and the trace's operator may be empty.

    For details about the relationship between IAM identities and operators and the operator username format, see Relationship Between IAM Identities and Operators.

    Trace Status

    Select one of the following options from the drop-down list:

    • normal: The operation succeeded.
    • warning: The operation failed.
    • incident: The operation caused a fault that is more serious than a normal failure, for example, causing other faults.

    Enterprise Project ID

    ID of the enterprise project to which a resource belongs.

    To check enterprise project IDs, go to the Enterprise Project Management Service (EPS) console and choose Project Management in the navigation pane.

    Example: b305ea24-c930-4922-b4b9-******1eb2

    Access Key

    Temporary or permanent access key ID.

    To check access key IDs, hover over your username in the upper right corner of the console and select My Credentials from the pop-up list. On the displayed page, choose Access Keys in the navigation pane.

    Example: HSTAB47V9V*******TLN9

  5. On the Trace List page, you can also export and refresh the trace list, and customize columns to display.

    • Enter any keyword in the search box and press Enter to filter desired traces.
    • Click Export to export all traces in the query result as an .xlsx file. The file can contain up to 5,000 records.
    • Click to view the latest information about traces.
    • Click to customize the information to be displayed in the trace list. If Auto wrapping is enabled (), excess text will move down to the next line; otherwise, the text will be truncated. By default, this function is disabled.

  6. (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.
  1. Log in to the CTS console.
  2. In the navigation pane, choose Trace List.
  3. Each time you log in to the CTS console, the new edition is displayed by default. Click Old Edition in the upper right corner to switch to the trace list of the old edition.
  4. In the upper right corner of the page, set a desired query time range: Last 1 hour, Last 1 day, or Last 1 week. You can also click Customize to specify a custom time range within the last seven days.
  5. Set filters to search for your desired traces.

    Table 2 Trace filtering parameters

    Parameter

    Description

    Trace Type

    Select Management or Data.

    • Management traces record operations performed by users on cloud service resources, including creation, modification, and deletion.
    • Data traces are reported by OBS and record operations performed on data in OBS buckets, including uploads and downloads.

    Trace Source

    Select the name of the cloud service that triggers a trace from the drop-down list.

    Resource type

    Select the type of the resource involved in a trace from the drop-down list.

    For details about the resource types of each cloud service, see Supported Services and Operations.

    Operator

    User who triggers a trace.

    Select one or more operators from the drop-down list.

    If the value of trace_type in a trace is SystemAction, the operation is triggered by the service and the trace's operator may be empty.

    For details about the relationship between IAM identities and operators and the operator username format, see Relationship Between IAM Identities and Operators.

    Trace Status

    Select one of the following options:

    • Normal: The operation succeeded.
    • Warning: The operation failed.
    • Incident: The operation caused a fault that is more serious than a normal failure, for example, causing other faults.

  6. Click Query.
  7. On the Trace List page, you can also export and refresh the trace list.

    • Click Export to export all traces in the query result as a CSV file. The file can contain up to 5,000 records.
    • Click to view the latest information about traces.

  8. In the Tampered or Not column of a trace, check whether the trace is tampered with.

    • No: The trace is not tampered with.
    • Yes: The trace is tampered with.

  9. Click on the left of a trace to expand its details.

  10. Click View Trace in the Operation column. The trace details are displayed.

  11. (Optional) On the Trace List page of the old edition, click New Edition in the upper right corner to switch to the Trace List page of the new edition.