Deze pagina is nog niet beschikbaar in uw eigen taal. We werken er hard aan om meer taalversies toe te voegen. Bedankt voor uw steun.
- What's New
- Function Overview
- Service Overview
- Getting Started
- User Guide
- Best Practices
- API Reference
- SDK Reference
-
FAQs
- Must I Use an IAM User (Sub Account) to Configure Transfer on CTS and Perform Operations on an OBS Bucket?
- How Will CTS Be Affected If My Account Is in Arrears?
- What Are the Recommended Users of CTS?
- What Will Happen If I Have Enabled Trace Transfer But Have Not Configured an Appropriate Policy for an OBS Bucket?
- Does CTS Support Integrity Verification of Trace Files?
- Why Are There Some Null Fields on the View Trace Page?
- Why Is an Operation Recorded Twice in the Trace List?
- What Services Are Supported by Key Event Notifications?
- How Can I Store Trace Files for a Long Time?
- Why Are user and source_ip Null for Some Traces with trace_type as SystemAction?
- How Can I Find Out Who Created a Specific ECS?
- How Can I Find Out the Login IP Address of an IAM User?
- Why Are Two deleteMetadata Traces Generated When I Buy an ECS in Pay-per-Use or Yearly/Monthly?
- What Can I Do If I Cannot Query Traces?
- Can I Disable CTS?
- How Do I Configure the Storage Duration of CTS Audit Logs to 180 Days?
- What Should I Do If I Cannot Enable CTS as an IAM User?
- How Do I Enable Alarm Notifications for EVS?
- Videos
Fault Locating
Scenario
If a resource or an action encounters an exception, you can query operation records of the resource or action in a specified time period and view the requests and responses to facilitate fault locating.
Prerequisites
You have enabled CTS and trackers are running properly.
Procedure (for Old Console)
The following shows how to locate an ECS fault which occurred in a morning.
- Log in to the management console as a CTS administrator.
- Click
in the upper left corner to select the desired region and project.
- Click
in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.
- Choose Trace List in the left navigation pane.
- Set filters in sequence and click Query.
NOTE:
Select Management for Trace Type, ECS for Trace Source, ecs for Resource Type, Resource ID for Search By, and enter the ID of the faulty virtual machine (VM). In the upper right corner, select a time range from 06:00:00 to 12:00:00 on the day when the fault occurred. Then, click Query to view the result.
- Check the returned traces, especially the request type and response of each trace. Pay attention to traces whose status is warning or incident, and traces whose response indicates a failure.
- Log in to the management console as a CTS administrator.
- Click
in the upper left corner to select the desired region and project.
- Click
in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.
- Choose Trace List in the left navigation pane.
- Select Management for Trace Type, ECS for Trace Source, ecs for Resource Type, and Warning for Trace Status. In the returned traces, locate the trace named createServer.
- Check the trace details and locate the fault based on the error code or error message.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.