Logs tab
Gateway Logs list, in chronological order, the system events, connection changes, and protocol errors generated in real time by the gateway software in the field. When a connectivity issue arises, a device stops responding, or a connector behaves unexpectedly, this tab helps you pinpoint the root cause quickly.
Logs consist of four columns: TIME, LEVEL, SOURCE, and MESSAGE. The level filter and Live mode let you navigate through hundreds of records with ease.
Log Table Structure
The example table below shows log records sourced from a real gateway. Each row contains the exact time of the event, its level, source, and a detailed message.
Log Levels
Every log entry carries a level badge that instantly communicates the criticality of the event and indicates which records need to be reviewed first.
ERROR — Error
A critical error occurred in the connector or protocol layer. The device is not responding, connection failed, or an unexpected data format was received. These logs should be reviewed first.
WARNING — Warning
The system is still operational but a condition requiring attention occurred — a connection dropped temporarily, a reconnect attempt was made. Investigate if it repeats persistently.
INFO — Information
Informational messages about normal operation flow. Reports events like connection established, reconnected, or a task completed successfully. Useful for debugging and audit trails.
Filters and Controls
The toolbar at the top of the log screen provides several essential controls for navigating thousands of records quickly:
Log Data Flow
Gateway logs reach the platform via the following pipeline:
Event Generated
A connector or protocol module generates an event (error, warning, or info).
Log Buffer
The gateway buffers the log locally; records are retained even if connectivity drops.
Cloud Transfer
Securely transmitted over TLS to the SolarTools cloud infrastructure.
Platform View
Listed in real time on the Logs tab; monitorable with filters and Live mode.
Debugging Tip
When investigating repeating ERROR logs, reference the SOURCE column. If the same source module (e.g. pymodbus.logger) is generating errors repeatedly, check the IP/Port settings of the related connector — the device is most likely unreachable.
Using Live Mode
Keep Live mode enabled during field tests. When a connector is restarted or a Deploy Config is applied, you will see the logs update instantly. This is the fastest way to validate configuration changes in real time.