# Check and manage Module Log

### PUQcloud Panel

##### [Order Now](https://puqcloud.com/puqcloud-panel.php) | [Download](https://github.com/puqcloud/PUQcloud) | [FAQ](https://faq.puqcloud.com/)

#### Overview

The **Module Log** in **PUQcloud Panel** provides detailed records of all operations executed by modules — including API requests, SSH commands, and service actions.  
It helps administrators **debug**, **monitor**, and **audit** communication between PUQcloud and external systems such as **Proxmox**, **Nextcloud**, and others.

All logging processes run **in the background**, allowing multiple modules to record events simultaneously **without impacting performance**.  
This ensures that even heavy automation tasks remain fast and efficient.

- - - - - -

#### Navigation Path

**Dashboard → Monitoring → Module Log**

- - - - - -

#### Key Features

<table id="bkmrk-feature-description-"><thead><tr><th>Feature</th><th>Description</th></tr></thead><tbody><tr><td>**Detailed Module-Level Tracking**</td><td>Records every request and response for each module.</td></tr><tr><td>**Safe Background Execution**</td><td>All logs are generated asynchronously to avoid slowing down the system.</td></tr><tr><td>**Live Monitoring**</td><td>Real-time updates every few seconds for active debugging.</td></tr><tr><td>**Filter by Date and Time**</td><td>Review specific activity ranges.</td></tr><tr><td>**Search and Filter**</td><td>Quickly locate logs by module name, action, or keyword.</td></tr><tr><td>**Log Viewer**</td><td>Inspect full request and response content for debugging.</td></tr><tr><td>**Delete All Logs**</td><td>Instantly clear old logs when troubleshooting is complete.</td></tr></tbody></table>

- - - - - -

#### Using the Module Log

##### 1. Access the Page

Navigate to  
**Dashboard → Monitoring → Module Log**

You’ll see all module-related activity displayed in a structured table with columns for:

- **Date**
- **Name** (module name)
- **Action**
- **Level**

[![Module Log Overview](https://doc.puq.info/uploads/images/gallery/2025-10/scaled-1680-/Kxn1.png)](https://doc.puq.info/uploads/images/gallery/2025-10/Kxn1.png)

- - - - - -

##### 2. Filter by Date and Time

To focus on a specific period, use the **Filter** control at the top.  
Select the desired start and end dates and times, then click **Apply** to reload the results.

[![Date Range Filter](https://doc.puq.info/uploads/images/gallery/2025-10/scaled-1680-/ogC2.png)](https://doc.puq.info/uploads/images/gallery/2025-10/ogC2.png)

- - - - - -

##### 3. View Log Details

Each record includes a “View” (👁️) icon on the right.  
Click it to open the detailed log window showing:

- **Type and Module Name**
- **Action Type**
- **Log Level**
- **Request Payload**
- **Response Data**

This view is essential for debugging API and SSH communication.

[![Log Detail View](https://doc.puq.info/uploads/images/gallery/2025-10/scaled-1680-/mAb3.png)](https://doc.puq.info/uploads/images/gallery/2025-10/mAb3.png)

- - - - - -

#### Columns Explained

<table id="bkmrk-column-description-d"><thead><tr><th>Column</th><th>Description</th></tr></thead><tbody><tr><td>**Date**</td><td>Timestamp of the log entry.</td></tr><tr><td>**Name**</td><td>The name of the module (e.g., puqProxmox, puqNextcloud).</td></tr><tr><td>**Action**</td><td>Describes what operation was executed (API Request, SSH Command, etc.).</td></tr><tr><td>**Level**</td><td>Indicates the log type (Debug, Info, Warning, Error).</td></tr></tbody></table>

- - - - - -

#### Log Levels

<table id="bkmrk-level-description-%F0%9F%9F%A3-"><thead><tr><th>Level</th><th>Description</th></tr></thead><tbody><tr><td>🟣 **DEBUG**</td><td>Detailed technical data for developers and administrators.</td></tr><tr><td>🟦 **INFO**</td><td>Informational events indicating normal operation.</td></tr><tr><td>🟧 **WARNING**</td><td>Non-critical issue or irregular response.</td></tr><tr><td>🔴 **ERROR**</td><td>Operation failed or received invalid data.</td></tr></tbody></table>

- - - - - -

#### Controls and Options

<table id="bkmrk-control-description-"><thead><tr><th>Control</th><th>Description</th></tr></thead><tbody><tr><td>**Auto Refresh**</td><td>Refresh interval (top-right) allows you to monitor logs in real time.</td></tr><tr><td>**Off/On Switch**</td><td>Enable or disable live updates.</td></tr><tr><td>**Search Box**</td><td>Quickly find logs by action or module name.</td></tr><tr><td>**Delete All**</td><td>Clears all logs at once — useful after debugging sessions.</td></tr></tbody></table>

- - - - - -

#### Example Use Case

While testing the **puqProxmox** module, the administrator can open **Module Log** to check the API and SSH calls executed during a provisioning process.

Example entry:

```
2025-10-28 08:25:23 | puqProxmox | API Request - Sending Request | DEBUG

```

By clicking the 👁️ icon, the admin can inspect both the request JSON and the response received from the external system.

- - - - - -

#### Tips

- Use **DEBUG** level logs for troubleshooting module integrations.
- Regularly clear old logs to keep your workspace clean.
- Combine with the **Task Queue** section to trace background automation steps.
- Since logs are recorded asynchronously, there’s **no performance degradation**, even during heavy module execution.