Halaman ini belum tersedia dalam bahasa lokal Anda. Kami berusaha keras untuk menambahkan lebih banyak versi bahasa. Terima kasih atas dukungan Anda.
- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- CodeArts PerfTest Use Process
- Permissions Management
- Test Resource Management
- PerfTest Project Management
-
PerfTest Case Management
- Test Case Description
- Directory Management of Test Cases
- Creating a Test Case
-
Configuring a Test Case (High-Performance Test Projects)
- Filling in Case Details
- Configuring a Case Script
- Adding Request Information (Packet)
- Adding Request Information (Think Time)
- Adding Request Information (Response Extraction)
- Adding Request Information (Checkpoint)
- Adding a Data Instruction, Cycle Controller, Condition Judgment, or Rendezvous Point
- Adding Concurrency Weight Controllers and Throughput Controllers
- Pressure Configuration
- Advanced Configuration
- SLA Configuration
- Configuring a Test Case (Scalable Test Projects)
- Setting Global Variables (High-Performance Test Projects)
- Setting Global Variables (Scalable Test Projects)
- Binding a Domain Name
- Plug-in Management
- Resetting Configurations
- Managing Test Cases
- Debugging a Case
- Batch Operations
- PerfTest Task Management
- PerfTest Report Management
- Transaction Management
- JMeter Test Project Management
- Crontask
- Configuring SLAs
- Auditing
- Reference
- Best Practices
- API Reference
- SDK Reference
-
FAQs
- Resource Group Management
-
Pressure Test Project Management
- What Are the Differences Between Think Time and Duration in CodeArts PerfTest?
- What Is the Number of Concurrent Users?
- How Do I Fill in Packets?
- Why Does Transaction Debugging Frequently Fail?
- Which Headers Are Mandatory in an HTTP-based Packet Request?
- Why Is the CPU Usage of the Execution Node Used for the Pressure Test Constantly High?
- What Are the Differences Between Global Variables and Variables Extracted from Responses?
- What Is the Impact of the Bandwidth Applied for CodeArts PerfTest on Tests?
- What Are the Differences Between a JMeter Test Project and a PerfTest Project?
- How Do I Check If the Global Variable Values Are Read Sequentially in a Test Task?
- Pressure Test Report Management
-
General FAQs
- What Are the Permissions Required for Using CodeArts PerfTest?
- How Do I Use the New IAM Edition to Isolate Permissions by Enterprise Project?
- Does CodeArts PerfTest Support Windows Server 2016 Standard (64-bit)?
- What Can I Do If Chinese or Special Characters Are Not Properly Displayed When the API Response Body Containing Them Is Exported Using the Traffic Recording Plug-in?
-
Using JMeter Projects
- What Are the Differences Between the JMeter Engine of CodeArts PerfTest and the Open-source JMeter?
- What Scripts Does the JMeter Engine of CodeArts PerfTest Support?
- Which Operations in Scripts Are Not Supported by the JMeter Engine of CodeArts PerfTest?
- What Are the Possible Causes of a JMX File Import Error in a JMeter Test Project?
- What Are the Suggestions for Using CodeArts PerfTest Scripts?
- How Do I Use the Global Variable Function?
- What Should I Pay Attention to When Uploading a Third-Party JAR Package?
- What Should I Pay Attention to When Uploading a CSV File?
- What Should I Pay Attention to When Uploading a Custom Installation Package?
- Why Does CodeArts PerfTest Return Garbled Characters When Content-Type in the Request Header Is Set to UTF-8 in JMeter?
- What Are the Meanings of Log Errors in a JMeter Report?
- Why Does JMeter Case Debugging Fail in Less Than 5 Seconds and No Data Is Displayed on the Page?
- Videos
- General Reference
Copied.
Viewing CTS Traces in the Trace List
Scenarios
After you enable CTS and the management tracker is created, CTS starts recording operations on cloud resources. After a data tracker is created, the system starts recording operations on data in Object Storage Service (OBS) buckets. Cloud Trace Service (CTS) stores operation records (traces) generated in the last seven days.
These operation records are retained for seven days on the CTS console and are automatically deleted upon expiration. Manual deletion is not supported.
This section describes how to query or export operation records of the last seven days on the CTS console.
Constraints
- Traces of a single account can be viewed on the CTS console. Multi-account traces can be viewed only on the Trace List page of each account, or in the OBS bucket or the CTS/system log stream configured for the management tracker with the organization function enabled.
- You can only query operation records of the last seven days on the CTS console. To store operation records for longer than seven days, you must configure transfer to OBS or Log Tank Service (LTS) so that you can view them in OBS buckets or LTS log groups.
- After performing operations on the cloud, you can query management traces on the CTS console one minute later and query data traces five minutes later.
- Data traces are not displayed in the trace list of the new version. To view them, you need to go to the old version.
Viewing Real-Time Traces in the Trace List of the New Edition
- Log in to the management console.
- Click
in the upper left corner and choose Management & GovernanceManagement & Deployment > Cloud Trace Service. The CTS console is displayed.
- Choose Trace List in the navigation pane on the left.
- On the Trace List page, use advanced search to query traces. You can combine one or more filters.
- Trace Name: Enter a trace name.
- Trace ID: Enter a trace ID.
- Resource Name: Enter a resource name. 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.
- Resource ID: Enter a resource ID. Leave this field empty if the resource has no resource ID or if resource creation failed.
- Trace Source: Select a cloud service name from the drop-down list.
- Resource Type: Select a resource type from the drop-down list.
- Operator: Select one or more operators from the drop-down list.
- Trace Status: Select normal, warning, or incident.
- normal: The operation succeeded.
- warning: The operation failed.
- incident: The operation caused a fault that is more serious than the operation failure, for example, causing other faults.
- Enterprise Project ID: Enter an enterprise project ID.
- Access Key: Enter a temporary or permanent access key ID.
- Time range: Select Last 1 hour, Last 1 day, or Last 1 week, or specify a custom time range within the last seven days.
- 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.
- For details about key fields in the trace structure, see Trace Structuresection "Trace References" > "Trace Structure" and Example Tracessection "Trace References" > "Example Traces".
- (Optional) On the Trace List page of the new edition, click Go to Old Edition in the upper right corner to switch to the Trace List page of the old edition.
Viewing Real-Time Traces in the Trace List of the Old Edition
- Log in to the management console.
- Click
in the upper left corner and choose Management & GovernanceManagement & Deployment > Cloud Trace Service. The CTS console is displayed.
- Choose Trace List in the navigation pane on the left.
- Each time you log in to the CTS console, the new edition is displayed by default. Click Go to Old Edition in the upper right corner to switch to the trace list of the old edition.
- Set filters to search for your desired traces. The following filters are available.
- Trace Type, Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.
- If you select Resource ID for Search By, specify a resource ID.
- If you select Trace name for Search By, specify a trace name.
- If you select Resource name for Search By, specify a resource name.
- Operator: Select a user.
- Trace Status: Select All trace statuses, Normal, Warning, or Incident.
- Time range: Select Last 1 hour, Last 1 day, or Last 1 week, or specify a custom time range within the last seven days.
- Trace Type, Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.
- Click Query.
- 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.
- Click
on the left of a trace to expand its details.
- Click View Trace in the Operation column. The trace details are displayed.
- For details about key fields in the trace structure, see Trace Structuresection "Trace References" > "Trace Structure" and Example Tracessection "Trace References" > "Example Traces" in the CTS User Guide.
- (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.
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.
For any further questions, feel free to contact us through the chatbot.
Chatbot