1. Features and Objectives
The Logs module is designed to centrally record and audit operational activities and system events within the KiwiCloud console, enabling administrators to comprehensively track platform operation activities and system status. Through this module, users can trace every action in the device management and policy execution process, perform searches, export records, and retain historical logs to meet multiple needs such as compliance supervision, issue tracing, and security auditing.
The module consists of two functional tabs:
Operation History – Records all manual operations performed on the management console, including device management, policy configuration, application operations, and user & permission management.
System Logs – Records system-triggered events such as task scheduling, policy execution results, system alerts, and compliance enforcement.
Objectives:
Provide verifiable audit logs to meet corporate and industry compliance requirements;
Clarify operational accountability to support incident investigations and post-event reviews;
Quickly identify where and why faults occurred to shorten troubleshooting time;
Support log search and bulk export for report generation and long-term archiving.
2. Operation History
Operation History records all user-initiated actions within the KiwiCloud console, including device management, policy changes, application operations, announcement management, and account operations. The system displays each action’s details in chronological order, including:
Operation ID: A unique identifier for the action;
Module: The functional module where the action occurred (e.g., Personal Center, Device Management, Announcements);
Operation Type: The specific action performed (e.g., login, logout, create, modify);
Operation Reason: The reason provided by the user for performing the action;
Execution Result: Whether the action was successful;
Operation Log: Detailed log records related to the action (if applicable);
Duration: The time taken from initiation to completion (in milliseconds);
Operator: The account that performed the action;
Operator IP: The IP address of the device used to initiate the action;
Browser: The browser type and version used during the action;
Start Time / End Time: The start and end timestamps of the operation.
Administrators can quickly locate target records using Module Filter, Operation Type Filter, and Execution Result Filter, and can export results to meet compliance audit, issue tracing, and accountability needs.
This feature is suitable for:
Maintaining complete operation logs for auditing and compliance checks;
Quickly reconstructing operation paths to identify root causes when issues occur;
Identifying responsible parties for key actions and verifying execution results;
Providing operational evidence for dispute resolution and security incident reviews.
3. System Logs
System Logs record system events automatically executed in the background by the KiwiCloud platform. These include, but are not limited to, task scheduling, policy execution, system alerts, non-compliance handling, task cancellation, reopening, and issue resolution. Events are displayed in chronological order with detailed information, including:
Operation ID: A unique identifier for the event;
Module: The functional module that triggered the event (e.g., "My Tasks", "Device Management");
Operation Type: The specific event type (e.g., cancel, start processing, reopen, resolved);
Execution Result: Whether the system event was executed successfully;
Operation Log: Detailed records of event execution (if applicable);
Duration: The time taken from trigger to completion (in milliseconds);
Start Time / End Time: The timestamps marking when the event began and ended.
Administrators can quickly locate target events using Module Filter, Operation Type Filter, and Execution Result Filter, and export logs for audit retention and issue analysis.
Primary Uses:
Tracking the execution process and results of automated platform tasks;
Monitoring backend actions such as policy execution, system fixes, and non-compliance handling;
Quickly locating system execution records and verifying results during incident investigations;
Providing a complete backend event evidence chain for compliance audits and security analysis.