Document Purpose
This guide defines the functionality of Change Logs within the YieldPlanet system. It covers the purpose of operation tracking, how to access history, and methods for filtering event data.
1. Core Functionality: Change Logs
Change Logs represent the comprehensive operations history recorded within the YieldPlanet system. The tool tracks all registered events to ensure transparency and provide users with a complete audit trail of system modifications.
- Objective: To provide a searchable record of all operations performed within the tool.
- Scope: All registered system events and user-initiated operations.
2. Accessing and Reading Logs
Users can access the history of registered events to verify system changes or investigate specific operation details navigating through Tools > ChangeLogs
- Activity Tracking: Every operation is logged with specific metadata (timestamp, user, action).
- Data Integrity: The system strives for a 1:1 record of all operations performed.
3. Filtering Logs
To locate specific information within a high volume of data, use the filtering functions. This allows for targeted retrieval based on specific parameters.
- Search Criteria: Filters can be applied to narrow down results by date, user, or operation type.
Optimization Tip: Use specific filters to reduce noise and identify the exact sequence of events for a given period.
Key Terms Summary
| Term | Definition |
|---|---|
| Change Logs | A historical record of all operations and events registered in the system. |
| Operations History | The sequential list of actions performed by users or automated system processes. |
| Filtering | The process of applying specific parameters to view a subset of the log data. |