检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
User Guide Key Operations on ECS Key Operations on OBS 02 Start You can quickly get familiar with the CTS usage process through CTS Interactive Walkthroughs.
Why Are Two deleteMetadata Traces Generated When I Buy an ECS in Pay-per-Use or Yearly/Monthly? During ECS creation, metadata is used to store temporary information. When the creation is finished, the information is automatically deleted.
Using Cloud Eye for Real-time Monitoring and Alarm Reporting on Key Events CTS records key audit traces, such as deleteServer, deleteVpc, and deleteVolume, for cloud services like ECS, VPC, or EVS, and sends them to Cloud Eye.
Does CTS Record ECS Creation Failures? Yes. When you create an ECS, the operation and its result will be reported to CTS. How It Works With CTS, you can record ECS operations for later query, auditing, and backtracking.
If the ECS was created by an account, the IAM user name and the account name are the same.
You can perform the following operations on a trace file: Trace file creation and storage When you add, delete, or modify resources on services interconnected with CTS, such as Elastic Cloud Server (ECS), Elastic Volume Service (EVS), and Image Management Service (IMS), the target
ECS Server Creation EVS Disk Creation ECS Server Creation { "trace_id": "cbdd4480-2e03-11ef-82de-cf140e2a70fb", "trace_name": "createServer", "resource_type": "ecs", "trace_rating": "normal", "api_version": "1.0", "source_ip": "124.71.93.243", "domain_id
Public services, such as Elastic Cloud Server (ECS), Elastic Volume Service (EVS), Object Storage Service (OBS), Virtual Private Cloud (VPC), Elastic IP (EIP), and Image Management Service (IMS), are shared within the same region.
Supported Services and Operations Table 1 Supported services and operations Category Cloud Service Operations Compute Elastic Cloud Server (ECS) ECS operations that can be recorded by CTS Image Management Service (IMS) IMS operations that can be recorded by CTS Auto Scaling (AS) AS
The trace file storage path is as follows: OBS bucket name/CloudTraces/Region/Year/Month/Day/Tracker name/Cloud service Example: User-defined name/CloudTraces/ap-southeast-1/2016/5/19/system/ECS The trace file naming format is as follows: Trace file prefix_CloudTrace_Region/Region-project_Time
For example, you can grant ECS users only the permissions for managing a certain type of ECSs. Most policies define permissions based on APIs. For the API actions supported by CTS, see Table 1.
A digest file is stored in the following path: OBS bucket name/CloudTraces/Region/Year/Month/Day/Tracker name/Digest/Cloud service Example: OBS bucket name/CloudTraces/Region/2016/5/19/system/Digest/ECS Digest File Name Format The digest files are named as follows: Trace file prefix_CloudTrace-Digest_Region
CTS sends notifications of all key operations on services including ECS, EVS, VPC, DEW, native OpenStack, and IAM. These operations include creation, deletion, login, and native OpenStack API calls.
Set filters as follows: Select ECS for Trace Source, ecs for Resource Type, and warning for Trace Status. For failed ECS creation operations, view the trace named createServer in the filtering result.
Select Management for Trace Type, ECS for Trace Source, ecs for Resource Type, Resource ID for Search By, enter the ID of the VM, and click Query. By default, the matching traces generated in the last hour are returned.
Example: CloudTraces/eu-de/2017/11/15/Digest/ECS/tGPYa_CloudTrace-Digest_eu-de_2017-11-15T10-12-10Z.json.gz. String digestObject = "digestObject"; // Directly writing AK/SK in code is risky.