# Logs ## Overview The **Logs** section serves as a comprehensive audit trail for key actions and changes within the platform. It helps administrators, managers, and support teams track what happened, when, and who performed the action. This visibility is essential for maintaining accountability, diagnosing issues, and ensuring data consistency across the system. Logs are categorized into five main types for clarity and ease of navigation: #### **1. General Logs** These logs capture broad system-level operations related to devices and clients. Whether it's importing devices, editing configurations, or managing user access, this category helps ensure that all significant actions are traceable. It’s particularly useful for onboarding processes, troubleshooting, and understanding system-wide changes over time. #### **2. Miner Logs** Focused specifically on individual mining devices, this category logs operational and configuration changes, including reboots, pool changes, or resets. It’s helpful for identifying technical issues, tracking miner lifecycle events, and understanding the sequence of interventions made by different users or automated systems. #### **3. Client Logs** This section tracks changes made to client profiles and their associated billing records. From contact information updates to tariff adjustments and payment entries, these logs provide transparency in client management. They are especially valuable for financial auditing, resolving disputes, and maintaining accurate service records. #### **4. Task Logs** Task logs provide insight into the creation, assignment, and progress of tasks within the team. Any changes in status, deadlines, priorities, or descriptions are recorded here. These logs are instrumental in project management and team coordination, allowing you to follow the evolution of a task and hold contributors accountable. #### **5. Admin Logs** These logs cover administrative actions affecting system-wide settings, such as managing staff, roles, facilities, or automation rules. Monitoring these changes is crucial for maintaining system integrity and security. They help ensure that sensitive operations—like permission adjustments or infrastructure changes—are fully documented. ## W**hy It’s Helpful** * **Transparency:** Everyone can see what actions have been taken, reducing ambiguity and miscommunication. * **Accountability:** You can easily identify who made specific changes, which is vital for team oversight and error tracking. * **Troubleshooting:** When an issue arises, logs provide the context needed to understand the cause and act quickly. * **Audit readiness:** Logs support compliance and auditing processes by providing a reliable historical record of activities. * **Efficiency:** By knowing what’s already been done, teams can avoid redundant actions and streamline their workflows. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.moonone.online/audit/logs.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.