# Module Log

The **Module Log** tab provides insight into the logs generated by the selected module. The available logging features depend on the module’s implementation and capabilities.

If the module is built using the **Nexus Device SDK**, it supports **structured historical logging** as well as **real-time log streaming** from the device to the platform. For modules that do not use the SDK, basic console output may still be available.

<figure><img src="/files/rgOefxATV8pJyhQhKB7z" alt=""><figcaption><p>Module Log tab of a Selected Module</p></figcaption></figure>

The tab is divided into two views:

* **Historical Log**\
  Displays a paginated list of structured log entries collected from the module. This view is available **only for modules that support the Nexus SDK**, and allows filtering, searching, and expanding log entries for full detail as well as real-time streaming of logs directly from the Module to the browser.
* **Console Log**\
  Streams the last 300 Log lines of standard output and error messages from the module container, if supported by the device runtime. This view provides basic runtime visibility even for non-SDK modules.

> 💡 When SDK-based logging is available, the platform enables advanced features such as log-level filtering, grouping, and live updates.

{% hint style="info" %}
As default, Logs are send from the Module with a 5 minute interval. If Logs doesnt appear right away, please wait a few minutes, and refresh the historical view or enable the Live Stream Log radio button. This forces the device to stream the logs directly to the Browser in real-time.

Alternatively you can always use the Console Logs, which immidiatly retrieves and displays the last 300 Log Lines from the Module.
{% endhint %}

***

### Historical Log

The **Historical Log** view displays a structured, paginated list of recent log messages emitted by the selected module. Each entry includes metadata to support efficient filtering, sorting, and analysis.

**Tool Bar**

The historical Log has a toolbar in the top of the page

<figure><img src="/files/h61clvBwms8PXwHMjyaT" alt=""><figcaption><p>Historical Log Toolbar</p></figcaption></figure>

* **Module Log Level Setting**\
  This setting is available for all modules utilizing the Nexus SDK. It allows you to control the log output by specifying a log level filter, determining the severity of logs that the module should send
  * *Default Setting* The default log level is set to 'Error', meaning only error messages will be sent
  * *Verbose Setting* the log level to 'Verbose' enables the module to send all logs regardless of severity. This includes debug, informational, warning and error messages

Use this setting to customize logging behavior based on your monitoring and debugging needs

* **Live Stream Log**\
  When enabled, new log messages are streamed in real-time into the table without requiring manual refresh. It is a good idea to order the log table on the Timestamp column, so the most recent streamed logs are shown in top
* **Refresh**\
  Reloads the log list to show the most recent entries
* **Search Field**\
  Allows filtering logs by message content.

**Log Table**

The Log Table shows each Log item (Log Line). The Table has 3 columns, that can be ordered and it supports grouping of colums as well.

<figure><img src="/files/tIF09QoZanVnSrNmXXQO" alt=""><figcaption><p>Live Streaming of Module Log</p></figcaption></figure>

1. **Timestamp**\
   The exact time the log entry was generated, useful for correlating events across modules and devices.
2. **Level**\
   The severity of the message, such as:
   * `Information`
   * `Warning`
   * `Error`
   * `Debug`
   * `Verbose`

> 💡 *Log verbosity is configurable via the **Module Log Level** Setting dropdown.*

3. **Message**\
   A short summary of the log event (e.g., `JobEnded`, `DeviceConnectionStateChanged`, `Synchronizing Cold Path Measurements`).

> ➕ Clicking the **plus icon** to the left of a log entry expands the row to show full log details, such as structured data or stack traces (if provided).

***

### Console Log

The **Console Log** view provides a real-time snapshot of unstructured text output from the module’s standard output (stdout) and standard error (stderr) streams. This view is useful for live debugging or observing the raw behavior of the module as it runs.

<figure><img src="/files/rICiY0kUH1FXXkgsmDYS" alt=""><figcaption><p>Showing Console Log for a Custom Module (NodeRED)</p></figcaption></figure>

Unlike the **Historical Log**, which shows structured, indexed entries (available only for Nexus SDK-enabled modules), the Console Log presents raw line-based output similar to traditional terminal logs.

**Features and Controls**

* **Scroll to Bottom**\
  When enabled, the log view automatically scrolls to show the most recent messages, ensuring you’re always seeing the latest output.
* **Auto Refresh**\
  Automatically maintains the connection and updates the stream, even if new content is arriving rapidly.
* **Refresh Button**\
  Manually reloads the log output from the current module container.


---

# 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/module-details/module-log.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.