# Monitoring

The **Monitoring** tab in the Nexus Management Portal provides operators with a real-time view of individual device health, performance metrics, and module-level status. This interface is essential for diagnosing issues, understanding resource utilization, and verifying data pipeline activity.

## Monitoring UI Overview

<figure><img src="/files/sm0lCe9SmOaGdJoGWHzy" alt=""><figcaption><p>Showing Monitoring device page</p></figcaption></figure>

The **Monitoring** interface is organized into two main areas; Device/Module Tree and Details View for the selected Device or Module.

***

### Device/Module Tree (Left Panel)

The **Device/Module Tree** provides a hierarchical view of the monitored environment:

* **Management Endpoints** act as the top-level grouping. Devices are organized under the endpoints to which they have been provisioned.
* **Devices** appear as child nodes under each management endpoint, and can represent either an edge device or a standard IoT device, that does not have edge capabilities.
* **Modules** are shown under each device, representing the individual runtime components deployed to that device.

You can select any node in the tree—management endpoint, device, or module—to inspect detailed information in the right-hand pane.

> Tip: Use the **filter bar** above the tree to quickly locate specific devices or modules by name.

> ⚙️ **Edge Devices vs. Standard IoT Devices**
>
> The Monitoring UI will automatically adapt to the capabilities of the selected device type.
>
> * **Edge Devices** run a local runtime and support advanced features such as **module deployment and lifecycle management** and **detailed monitoring**.
> * **Edge Devices with Nexus SDK** are devices that are implemented using the Nexus SDK. This enables additional capabilities, such as **streaming logs**, executing module level custom **commands** and real-time visibility into **data collection** activities.
> * **Standard IoT Devices** are typically more constrained and support only **basic monitoring** (e.g., connectivity status and limited telemetry). They do not support module deployment.
>
> 💡 The Monitoring UI dynamically adapts to each device’s capabilities—displaying only the features supported by the selected device.

***

### Details View (Right Panel)

The **Details View** dynamically updates to reflect the entity currently selected in the Device Tree:

* When a **management endpoint** is selected, the view provides an overview of that endpoint’s devices.
* When a **device** is selected, the view shows comprehensive real-time monitoring data, including health status, metrics, deployed modules, data connectors, and reported issues.
* When a **module** is selected, the view displays module-specific diagnostics, such as runtime status, errors, version information, and connection state (if applicable).

This split-view layout allows operators to quickly navigate between devices and their components while maintaining context for both hierarchical structure and individual status.

<figure><img src="/files/3sypSIxNUpHOvahVEQSW" alt=""><figcaption><p>Module Details frontpage</p></figcaption></figure>

Each Device Tree node type is described in the following subpages.


---

# 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://docs.tricloudnexus.io/management-portal/operations/monitoring.md?ask=<question>
```

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.