Viewing RFS Logs in CTS
When you enable CTS, it begins to record operations performed on RFS resources. On the CTS console, you can query operation records from the last 7 days by performing the following operations.
Procedure
- Log in to the CTS console.
- In the navigation pane, click Trace List.
- Filter the desired operation events.
The trace list supports four filter types:
- Trace Source, Resource Type, and Search By
Select the search criteria from the drop-down lists. For example, select RFS from the Trace Source drop-down list box.
From the Search By drop-down list, select a trace name. From the Search By drop-down list, select or enter a specific resource ID. From the Search By drop-down list, select or enter a specific resource name.
- Trace Status: Select one of All trace statuses, Normal, Warning, and Incident.
- Operator: Select a specific operator (a user other than an account).
- Time Range: You can query traces generated during any time range of the last seven days.
- Trace Source, Resource Type, and Search By
- Click on the left of a trace to expand its details.
- Click View Trace in the Operation column. A dialog box is displayed to show trace structure details.
{ "trace_id": "4073d5e1-6ee6-11ed-bb00-61c31199dcbc", "code": "200", "trace_name": "parseTemplateVariables", "resource_type": "template", "trace_rating": "normal", "source_ip": "10.172.131.218", "trace_type": "ApiCall", "service_type": "RFS", "event_type": "system", "project_id": "47cf611e636c4a73806e2731cc7fa471", "response": "{\"variables\":[{\"default\":\"jiayue_test_ecs\",\"description\":\"Your ECS name\",\"name\":\"ecs_name\",\"type\":\"\\\"string\\\"\"}]}", "resource_id": "", "tracker_name": "system", "time": "2022/11/28 14:31:12 GMT+08:00", "resource_name": "", "user": { "domain": { "name": "iaas_aos_n30000772_01", "id": "fcca06b017704dfcb36dcf1b2a29d151" }, "name": "cto_c30031067_dev", "id": "155ad09309994f92a5147529aa0ceb2f" }, "record_time": "2022/11/28 14:31:12 GMT+08:00" }
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.