Agents - Log Monitoring
In RCOM Agents, logs play a critical role in monitoring real-time activities, diagnosing issues, and verifying connectivity between the edge and the RCOM Gateway.
Each agent generates two distinct types of logs:
- Agent Logs – Track operational events, configuration changes, and connectivity between the agent runtime and the gateway.
- Process Logs – Capture the execution-level details of each process or module running under the agent.
Agent Logs
Agent logs represent the overall operational state of the agent itself.
These logs provide insights into:
- Connection status between the agent and the gateway
- Power or monitoring state changes
- Configuration updates or synchronization events
- Live logging activities
- Start/stop actions and command responses
From the Agent Details → Log tab, administrators can:
- View the complete chronological list of logs
- Filter logs by level (
INFO,WARNING,ERROR, etc.) - Identify exceptions marked with the ⚠️ exclamation icon for quick troubleshooting
- Adjust pagination or refresh to view the latest entries
Each log record includes:
| Field | Description |
|---|---|
| Time | Timestamp of when the log was generated. |
| Log Level | Indicates severity — FINE, INFO, WARNING, ERROR, SEVERE, etc. |
| Message | Details of the agent action or status update. |
| Exception | Displays “⚠️” if an error or unhandled exception occurred. |
Control your logs:
You can choose to transmit or display only selected log levels to focus on relevant information.
Logs of the selected type and higher are shown; others are excluded.
Available levels include:
SEVERE → ERROR → WARNING → INFO → CONFIG → FINE → FINER → FINEST
For example, selecting INFO displays logs tagged INFO, WARNING, ERROR, and SEVERE while ignoring lower-level entries.
Example:
A log may show:
INFO – Live logging stopped for rkh
or
Updating agent configuration from Gateway…
Process Logs
Each agent can host one or more processes, and each process maintains its own log stream.
While Agent Logs track the runtime, Process Logs capture the execution of individual operations such as device reads, web requests, or filtering actions.
To access them:
Agents → Manage Agents → [Select Agent] → Processes → [Select Process] → Log
Each process log entry records the activity of modules like ReadPoint, WebRequest, or Filter, showing detailed execution events.
Common details in Process Logs:
| Field | Description |
|---|---|
| Time | Timestamp of the log entry. |
| Component | Name of the process component (e.g., Readpoint_V1, WebRequest_V1). |
| Log Level | Severity indicator. |
| Message | Description of the event or status. |
| Exception | Displays “⚠️” if an error or unhandled exception occurred. |
Control Your Logs
Just like Agent Logs, process logs allow you to filter visible entries by log level.
Logs of the selected type and higher are included in the list:
SEVERE → ERROR → WARNING → INFO → CONFIG → FINE → FINER → FINEST
For example, choosing FINE shows all FINE, INFO, WARNING, ERROR, and SEVERE entries, excluding the more granular FINER and FINEST messages.
Example:
ERROR – WebRequest_V1: Error sending WebRequest: The operation was canceled.
FINE – Readpoint_V1: Status changed: OK (Collection with 1 tag sent)
Log Exceptions
Both Agent and Process logs may contain log exceptions, visually indicated with an exclamation mark (⚠️) under the Exception column.
Clicking the icon (if enabled) provides the detailed exception trace captured by the agent’s internal logger — useful for deep diagnostics or when forwarding issues to RCOM support.
log exception