Operation Logs

Feature Overview

Item	Content
Applicable Role	Operator
Navigation path	Settings > Activity & Notifications > Operation Logs
Page route	/user/user-space/operation-logs
Managed objects	Platform operation records, users, actions, methods, IP addresses, processing times, and results

Beginner Explanation

Operator operation logs are the audit trail for the platform console. Use them to trace changes that administrators made to accounts, tenants, permissions, rate-control rules, and system settings. They are not model-call or business-request logs.

Terms Quick Reference

Term	Description
Operator	The account that performed a platform administration action.; Confirm the identity first during an investigation.
Target object	The configuration, member, or tenant that was viewed or changed.; Compare it with the record on the affected page.
Operation result	The success, failure, or partial-success status of an action.; Review the error information for failed actions.
Audit scope	The log boundary visible to the current account.; Check permissions first when records are missing.

Prerequisites

1. The current account has permission to view operation logs.
2. You have opened Activity & Notifications > Operation Logs.
3. Before exporting logs, you have confirmed the export scope and recipient.

Page Description

The page provides filters, an operation-log list, and record details for tracing who performed an action, when it occurred, and whether it succeeded.

Area	Description
Start Time / End Time	Sets the query time range.
Search / Reset	Runs a query or clears the filters.
Export CSV	Exports logs in the current query scope.
Log table	Shows the time, user, action, method, IP address, processing time, and result.

Main Operations

View Operation Logs

1. Open Operation Logs, select a time range, and filter by operator, module, action type, result, or keyword.
2. Check the target time, operator, object, result, and source. If no record is returned, check the time zone and clear filters one at a time.
3. The target event should be uniquely identifiable. For duplicate names, narrow the range with a redacted object ID fragment and time.
4. Logs may contain account, IP, and business-object information and must be redacted before export, screenshots, or sharing.

View Operation Log Details

1. Click "Details" for the target record and inspect the request action, object, result, duration, and error summary.
2. Compare preceding and following events to determine whether the action completed and whether a subsequent failure occurred.
3. If information is insufficient, escalate with a redacted time, module, and error category. Do not copy Tokens, keys, cookies, or complete request bodies.
4. Use log details only for audit and diagnosis. Do not replay high-risk operations from the page.

Export Operation Logs

1. Open Settings > Activity & Notifications > Operation Logs.
2. Locate the target Operation Logs and click "Export CSV".
3. Review or complete the required fields shown on the page, and confirm the target object, scope, and current status.
4. For an action that changes data, permissions, status, or an external setting, confirm the impact and rollback path before clicking the final confirmation button.
5. After the action, return to the list or details page and verify the status, update time, or result message.

Parameter Quick Reference

Field Name	Required	Field Type	Example	Description
HTTP Method	No	Enum	GET	Filters logs by HTTP request method.
Result	No	Enum	Success	Filters logs by operation result.
Start Time	No	Date time	2026-07-13 09:00	The start time of the query range.
End Time	No	Date time	2026-07-13 10:00	The end time of the query range.
Time	System generated	Date time	2026-07-13 09:30	The time when the operation occurred.
User	System generated	Text	Example user	The account or user that performed the operation.
Action	System generated	Text	Update configuration	The operation behavior or API meaning.
Method	System generated	Text	POST	The method used by this request.
IP	System generated	Text	192.0.2.1	The source IP of the operation. Desensitize it in documentation.
Cost	System generated	Number	120 ms	The request or operation processing duration.
Result	System generated	Enum	Success	The operation execution result.

Pitfalls

• Do not change roles, members, login policies, Keys, or API rate-control rules without confirming the affected users and systems.
• UI entries can differ by role and tenant scope; verify the current account context before troubleshooting.
• Never copy complete Keys, AK/SK, tokens, or secrets into documentation, tickets, or screenshots.
• Operation logs may contain sensitive audit information such as accounts, IP addresses, API paths, and operation results.
• Export CSV exports real log data and is a high-risk action.
• Before exporting, narrow the time range and confirm the recipient.
• Do not write real accounts, IP addresses, API paths, customer names, tenant IDs, or internal error details in documentation.

Result Validation

Check Item	Success Signal	If Abnormal
Time filter	The log list refreshes for the selected time range.	Check whether the time range is too narrow.
Result field	The operation result is displayed.	Use the user and action fields to continue the investigation.
Export entry	The export button is visible when the account has permission.	Confirm whether the log data can be shared before exporting it.
Reset filters	Selecting Reset restores the default filters.	Refresh the page and set the query conditions again.

FAQ

Expected logs are missing

Symptom:

The target operation is not shown after you filter by time.

Possible cause:

The selected time range does not include the operation, or the current account cannot view that log scope.

Resolution:

Expand the time range and search again. If the record is still missing, verify the log-view permission.

Can logs be exported directly?

Symptom:

The page provides an Export CSV entry.

Possible cause:

The exported file may contain users, IP addresses, API paths, and operation results.

Resolution:

Confirm the purpose, scope, and recipient before export, and desensitize the file when required.

Why is a target record missing from operator logs?

Symptom:

The target administrator, tenant, or configuration change is not present in operator operation logs.

Possible cause:

The time range is incorrect, the action occurred in a user-side tenant, or the current account cannot view that type of audit record.

Resolution:

Expand the time range and confirm where the action occurred. Filter again by tenant, operator, and target object. If the record is still absent, check the audit collection and retention policies.

How should the Operation Logs page be exported or captured safely?

Symptom:

Page information is needed for troubleshooting, audit, or delivery.

Possible causes:

The page may contain accounts, email addresses, IP addresses, internal paths, tenant identifiers, Keys, or amounts.

Resolution:

Keep only the necessary fields and action context. Use opaque light-gray pixel mosaics for sensitive text and never share complete credentials or internal addresses.

What should I do when the Operation Logs page shows unexpected data?

Symptom:

A field, status, metric, or related object differs from the expectation.

Possible causes:

The page scope, time condition, role permission, or upstream setting does not match.

Resolution:

Record the redacted object, time, and result. Verify the entry and filters first, then check related pages and Operation Logs.

Notes

• Operation logs may contain user identities, IP addresses, and API paths. Do not distribute them without authorization.
• Narrow the time range before export to avoid including unrelated data.
• Export CSV exports real log data and is a high-risk action.
• Before exporting, confirm the time range, desensitization requirements, and recipient.
• Do not write real accounts, IP addresses, API paths, customer names, tenant IDs, or internal error details in documentation.

Next Steps

1. To verify member changes, go to Members.
2. To verify role changes, go to Roles.