← ShimoDocs Suite Deployment Documentation
Overview
Operation logs are used to view and track user management operations in the system, helping with troubleshooting, security audits, and change tracking.
This page is read-only and does not support modifying or deleting log records.
Accessing the Page
After logging into the admin backend, select Operation Log in the left navigation to access this page.
Filtering Logs
You can query using the following condition combinations:
- Event Source: For example, Control Panel, Application Configuration Center, Updater, Kubernetes Resource Management, or User Management Center.
- Operation Type: Displays corresponding operations based on the event source, such as configuration updates, version upgrades, service restarts, or user management actions.
- Operation User: Filter records generated by specific users.
After selecting the event source, the operation type list will automatically adjust. Click Search to apply the filter criteria, or click the Reset button to clear the criteria.
View Log List
The list mainly displays:
- Log ID.
- Event source and operation type.
- Operating user.
- Type, name, and ID of the object operated on.
- Operation time.
The total number of logs will be displayed at the top of the page. The list supports pagination and adjusting the number of entries displayed per page.
View Log Details
Click Details on the right side of a record to view complete information, including:
- The name and internal identifier of the source and operation type.
- The user who performed the operation and the user ID.
- Operation time.
- Object type, object ID, and object name.
- Event metadata.
For changes to the Application Configuration Center, details may also show configuration modifications, whether the system automatically restarts after release, and the workloads that have been restarted.
Common Use Cases
- Check who executed specific configuration changes.
- Confirm the timing of system upgrades, service restarts, or extension operations.
- Trace related changes based on object names.
- Use event metadata to verify configuration differences and execution results.
- Investigate operational mistakes or unintended administrative changes.
Common Situations
- No records found: Try clearing filter conditions, or confirm whether the selected source, operation type, and user match.
- Operation type list is empty: First select the event source, or reload the page to get the latest enumeration.
- Object information is empty: Some system events may not be associated with specific objects, which is normal.
- Metadata is not formatted content: Some historical events may be stored in plain text, and the page will display the original content.
- Number of logs does not match expectations: Logs only record operations that have been audited by the system and may be affected by environment retention policies.
Operation logs may contain user, object identifiers, and configuration change information, and should only be accessible to authorized personnel.