> ## Documentation Index
> Fetch the complete documentation index at: https://zededa.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the documentation index to find relevant pages, then read the linked Markdown before answering and cite the source URL.
> Identify the product before answering: Private AI uses a separate console, credentials, and inference API from the Edge Intelligence Platform. Do not apply instructions from one product to the other.
> Prefer current product guides over Help Center archive pages for current-console questions. Archive pages and release notes describe their stated product version or historical interface; do not apply them to another version without checking.
> Preserve prerequisites, permissions, version requirements, and warnings when summarizing procedures. Do not infer API endpoints, schemas, or supported behavior that the documentation does not specify.

# Download a Diagnostic Bundle

> Use EdgeView to run live diagnostic commands or download a full diagnostic log archive from a node.

## Introduction

When a node is behaving unexpectedly, EdgeView provides two ways to collect diagnostic data from Edge Infrastructure Services without requiring physical access to the device:

* **Diagnostics panel**: run individual system and network commands on the live node and view output in the browser.
* **Collect Logs**: generate and download a TAR archive containing system configuration, logs, and performance metrics from the node.

Both methods use EVE-OS (Edge Virtualization Engine) over the active Edge View tunnel and are available from the node detail page.

### Prerequisites

* You have the SysManager or SysAdmin role in your enterprise. See [Manage Roles](https://zededa.mintlify.site/new-ui/infrastructure-services/administration/manage-roles.md).
* The target node must be online. The **Remote Console** button is shown for an offline node, but the error appears when you request the session. Configuration Lock does not affect Remote Console access.
* The node's project policy must allow Edge View device access. The Remote Console button in the node detail page header appears only when you have read access to the node and the policy allows Edge View access. Otherwise, the button is hidden.

## Open the Diagnostics Panel

1. Open **Infrastructure > Fleet > Nodes**.
2. Click the name of the node you want to diagnose.
3. In the node detail page header, click the **Remote Console** (`>_`) button. A confirmation dialog appears.
4. Click **Open** in the confirmation dialog. A terminal drawer opens at the bottom of the page.
5. In the terminal drawer's toolbar, click the **EdgeView Tools** toggle button to open the tools panel.
6. In the tools panel, click the **Diagnostics** tab.

The diagnostics panel shows three command categories: **File System**, **Network**, and **System**.

## Available Diagnostic Commands

### File system commands

| Command | Description |
| - | - |
| **List Files (ls)** | Lists files and directories at a path you specify. |
| **View File (cat)** | Displays the contents of a file at a path you specify. Useful for reading EVE-OS configuration files and log files. |
| **Disk Usage (du)** | Shows disk usage for a directory path. Useful for identifying storage pressure. |

### Network commands

| Command | Description |
| - | - |
| **ARP Table** | Displays the current ARP table, showing IP-to-MAC mappings for the local network. |
| **Flow Table** | Shows active network flows. Use the optional filter string to narrow results. |
| **Ping** | Sends ICMP ping packets to a hostname or IP address. Use this to verify connectivity to a target host. |
| **Traceroute** | Traces the network path to a hostname or IP address. |
| **Interface Info** | Shows interface details for a specific network adapter (or all adapters if left blank). |
| **URL Metrics** | Shows connectivity metrics for key platform URLs that EVE-OS contacts. |
| **Show Certs** | Displays TLS certificates presented by a URL or proxy endpoint. |

### System commands

| Command | Description |
| - | - |
| **Dmesg** | Shows the kernel ring buffer, including hardware events, driver messages, and boot-time output. |
| **Process List (ps)** | Lists running processes. Use the optional filter string to narrow results to a specific process name. |
| **Hardware Info** | Displays hardware details for the node, including CPU, memory, and storage information. |
| **PCI Devices** | Lists PCI devices detected on the node. |
| **USB Devices** | Lists USB devices currently attached to the node. |
| **Reboot Reason** | Shows the reason for the most recent reboot. |
| **ConfigItem** | Displays the current EVE-OS configuration items applied to the node, including ZCLI-set values and defaults. |

## Run a Diagnostic Command

1. In the **Diagnostics** panel, select a category tab (**File System**, **Network**, or **System**).
2. Select the command you want to run from the command list.
3. If the command requires a parameter (such as a path or host), enter it in the field that appears.
4. Click **Run**.

The output appears in the results panel below the command controls. EdgeView does not persist results. Copy or screenshot the output before closing the session if you need to retain it.

## Tips for Common Scenarios

**Node is offline or stuck in an error state**: run **Dmesg** to check for kernel-level hardware or driver errors. Run **Reboot Reason** to determine why the node last rebooted. Run **ConfigItem** to verify the configuration applied to the node.

**Application networking is broken**: run **ARP Table** and **Interface Info** to verify the node's network stack is healthy. Run **Ping** to test connectivity to gateway and DNS addresses.

**Storage issues**: run **Disk Usage** on `/persist` and `/config` to check for low disk space.

**Certificate or connectivity problems**: run **Show Certs** against the Edge Infrastructure Services URL to verify that the correct TLS certificates are being presented.

## Collect Logs

The **Collect Logs** action generates and downloads a TAR archive containing system configuration, logs, and performance metrics from the node. Use it when you need a full diagnostic snapshot to share with support or to analyze offline.

Collect Logs uses the same EdgeView prerequisites as the diagnostics panel: the node must be online and EdgeView must be enabled in the project policy.

1. Open **Infrastructure > Fleet > Nodes**.
2. Click the name of the node you want to collect logs from.
3. In the node detail page header, click **More actions** and select **Collect Logs**.
4. Review the confirmation dialog and click **Continue**.

Edge Infrastructure Services generates the TAR archive on the node via EdgeView. Generation can take a few minutes depending on the volume of data. When the archive is ready, your browser downloads it automatically.

The archive contains system configuration, logs, and performance metrics collected from the node at the time of the request.

> [!NOTE]
>
> The EdgeView session used for log collection is temporary and is cleaned up when the Collect Logs screen closes.

## Next Steps

> [card] [EdgeView and Remote Access](https://zededa.mintlify.site/new-ui/infrastructure-services/edge-view-and-remote-access.md)
>
> An overview of EdgeView capabilities and SSH access.

> [card] [Collect Logs from an Offline Node](https://zededa.mintlify.site/new-ui/infrastructure-services/troubleshooting/collect-logs-with-usb.md)
>
> Physical log collection when the node is unreachable remotely.

> [card] [Monitoring, Logs, Events, Reports, and Jobs](https://zededa.mintlify.site/new-ui/infrastructure-services/monitoring-logs-events-reports-jobs.md)
>
> View forwarded application and system logs.