Device Details

When selecting a device, the Details View displays a comprehensive snapshot of the device’s current state. The available features are:

Tool bar

• Ping device Button that verifies if the device is online, by sending a message and awaiting a response.

• Device Configuration A shortcut to the device configuration page, where assets, applications and modules can be assigned.

• Refresh Performs a forced refresh of all information on the page, by getting information directly from the management endpoint, where the device is provisioned.

Connectivity Status

This section displays the latest connection status between the device and its assigned management endpoint. It includes:

• Connection State Indicates whether the device is currently connected or disconnected based on its heartbeat activity.

• Last Seen Timestamp of the most recent successful communication from the device (e.g., telemetry or ping).

• Last Ping Attempt and Last Successful Ping Results of the platform’s automated connectivity checks. These values help diagnose intermittent or persistent connectivity issues.

• Uptime (if Nexus DeviceMonitoring is deployed to the device) Shows the duration since the device was last restarted, providing insight into runtime stability.

Resource Metrics

This section provides time-series visualizations of the device’s system resource usage, given that the module supports the Nexus SDK. These metrics are collected and reported by the module if it is built using the Nexus SDK.

The charts help operators monitor resource consumption trends and identify performance bottlenecks, such as memory leaks or disk exhaustion. Metrics include:

• CPU Utilization (P99) Displays the 99th percentile of CPU usage over time, highlighting peak load behavior rather than average usage. This is useful for identifying resource spikes and understanding worst-case performance.

• Memory Usage Shows both used and total memory (in gigabytes), allowing you to assess how much RAM is available and whether the device is under memory pressure.

• Disk Usage Visualizes available disk space as a percentage of the total storage capacity. This helps detect devices approaching storage limits, which could impact data collection or module stability.

📊 These charts support configurable time windows, making it easier to correlate resource usage with recent events or issues.

Modules

The Modules section provides a detailed overview of all modules deployed to the selected device. For each module, the platform displays module name, version, current status, restart count and any reported errors. This view helps operators validate module health, detect misconfigurations, and monitor deployment activity in real time.

Module Lifecycle States

Each module reports one of the following lifecycle states:

• Starting The module has been declared in the desired deployment configuration, but the device has not yet reported its status. This typically occurs just after deployment and indicates that the module is being downloaded from the container registry and started up.

• Running The module is actively running and has reported a healthy state. This is the expected status during normal operation.

• Error The module has encountered a critical runtime error. This may result from a failed start-up, crash, misconfiguration, or dependency failure. A descriptive error messages (e.g., exit code) is shown, when available. Clicking the module state redirects to the module logs.

• Warning The module is running, but with non-critical issues. Examples include configuration issues or warnings emitted by the module runtime. These are useful for early detection of underlying problems. A descriptive error messages (e.g., exit code) is shown, when available.

• Stopping The module is still being reported by the device, but it is no longer part of the desired deployment configuration. This indicates the module is in the process of being stopped or cleaned up.

Data Connectors

The Data Connectors section provides visibility into the status of data collection modules deployed to the device. This feature is available only if the data collection modules are built using the Nexus Device SDK, which enables reporting of internal state and connection health.

Each row in the list represents a data collector module currently deployed to the device.

Expandable View

• Each module line can be expanded to show a list of endpoints.

• Endpoints represent the individual data sources or connections managed by the module.

🔍 Note: The definition of an "endpoint" depends on the protocol or data source type. For example:

OPC UA: Each endpoint corresponds to a different OPC UA server MQTT: Each endpoint corresponds to a subscribed topic Modbus: Each endpoint represents a slave device The DataDistribution module hosts formula-based calculations, which is also treated as a data collectors with an endpoint.

Endpoint Details

For each endpoint, the following details are shown:

• Endpoint Name A unique identifier representing the connection or source.

• State The current operational state of the endpoint, such as:

  • Stopped – data collection is deactivated

  • Running – data is being collected successfully

  • Reconnecting – endpoint is temporarily disconnected

  • Failure – data collection has failed or configuration is invalid

• Details Additional status information for error messages.

This granularity allows operators to quickly pinpoint which part of the data pipeline is experiencing issues, even when a module is connected to multiple sources.

Issues

The Issues section displays real-time problems detected by the DeviceMonitoring module. This feature is only available on devices where DeviceMonitoring is deployed and running.

Each issue represents a system-level condition that may impact device performance, stability, or data integrity. When an issue is detected, it is automatically logged in the UI and also triggers an alarm in the platform’s alerting system, allowing for immediate visibility and response.

Available Issue Types

Issues are primarily related to resource constraints and internal device health:

• CPU Usage Over Limit Triggered when the device’s CPU usage exceeds a defined threshold for a sustained period.

• Memory Under Limit Reported when available memory falls below a safe operating threshold, indicating possible memory exhaustion.

• Disk Space Under Limit Indicates that remaining disk space is too low to ensure stable operation or continued data collection.

• Inter-Module Communication Queue Count Too Large Occurs when internal message queues between modules exceed expected limits, potentially pointing to issues on processing or bottlenecks.

Issue Details

Each issue entry includes:

• Timestamp The exact time the condition was first detected. This helps correlate issues with events such as deployments, spikes in telemetry, or resource saturation.

• Description A detailed explanation of the issue, including measured values and thresholds. For example: “CPU usage at 97.3%, exceeding threshold of 85%”

⚠️ Issues are continuously monitored. When the underlying condition clears (e.g., resource usage returns to normal), the corresponding platform alarm is automatically set to RTN (Return To Normal). The operator still needs to acknowledge the alarm.