System Overview
Open System Overview to inspect the loaded project, collection health, alarms, forwarding targets, and host resources. Data refreshes automatically. Wait for loading to finish and compare successive samples before judging the current state.
Inspect the running gateway
First Look at Terms
| Terms | On-site Understanding |
|---|---|
| Channels | Communication links from gateways to field devices, such as a TCP connection, a serial port, or a listening port. |
| Device | a PLC, instrument, acquisition module, or a logic acquisition object managed by plugins. |
| Variable | A point in the point list, such as temperature, pressure, operating status, fault state, or control write point. |
| Real-time alarms | Alarm events that still require personnel attention do not mean the on-site fault has been resolved. |
| CPU/memory/disk | gateway host resources. If the data remains high for a long time, prioritize checking collection frequency, forwarding cache, rule flow, and log volume. |
Page Entry
After logging into the system, the system overview page is displayed by default, or you can click the "System Overview" menu on the left to enter.
Statistics Card
| Card | Description |
|---|---|
| Collection devices | Compare the configured total with the online count. Inspect offline devices in Collection Configuration. |
| Total number of variables | Displays the total number of variables and indicates the number of normal variables. |
| Real-time Alarm | Shows alarm-variable and event counts requiring attention. These are not counts of equipment failures. |
| Forwarding targets | Compare total and online targets, then verify their actual output at the receiver. |
Statistical cards are suitable for quickly determining whether the project is fully loaded. If abnormalities are found in the number of device online counts, normal variable counts, or real-time alarm counts, then proceed to "Collection Configuration," "Real-time Alarms," or "System Logs" to view details.
Cards without permission may be hidden. An unavailable or not-yet-loaded count can display —; do not record it as zero. A failed refresh can retain the last successful value, so check status and collection time for freshness. View channel counts in Collection Configuration → Channel Management.
Variable totals can include memory variables and automatically created status variables. Compare configured totals, licensed capacity, and currently online/healthy counts separately; they do not have to equal the PLC point-table row count.
Trace a real reading
- Open a known collection point and compare its value, raw value, quality, and advancing collection time with the source.
- Check the associated device plugin, execution interval, and channel endpoint. Network connectivity alone does not validate a protocol address.
- In a permitted test environment, stop the source and observe offline quality. A retained last value does not prove new sampling.
- Restart the same source without recreating the channel, device, or variable. Verify restored quality and advancing time.
- If forwarding is configured, verify a new message at an independent receiver. See Collection debugging.
Page Layout
The overview uses a fixed order for statistics, system resources, project information, and trends. Columns adapt to the available width. If a section is missing, check the account permission and loading state. Change collection or forwarding tasks on their configuration pages.
Project Information
Project Information Displays basic information about the currently operating project:
| Information | Description |
|---|---|
| Project Name | The currently loaded project name. |
| Firmware Version | TGateway Version Number. |
| Serial Number | Gateway serial number or UUID. |
| AOT release | Whether it is an AOT release package. AOT packages can usually run independently, but plugin compatibility must be confirmed before release. |
| Maximum number of channels authorized | Maximum number of channels currently authorized for authorization. |
| Maximum number of authorized devices | Maximum number of devices currently allowed by the authorization. |
| Maximum number of authorized variables | Maximum number of variables currently allowed by authorization. |
| Project generation time | Time recorded when the loaded project information was saved or generated. It is not the current Runtime startup time. |
| Project description | Description of the loaded project. |
If project information is empty or shows abnormal, first confirm whether the current user has permission to view project information, then check whether TGateway loads the project correctly.
Monitor system resources
System Resource Monitoring
| Metrics | Description |
|---|---|
| CPU Usage | System CPU Usage Percentage. If the rate remains high, prioritize high-frequency collection, rule processes, and data forwarding. |
| Memory usage | System memory usage percentage. If persistently high, check the number of variables, cache queues, and runlogs. |
| Disk Usage | Used and total capacity of the disk containing the gateway program. Insufficient space can affect history, cache files, and logs. |
| Process memory, GC memory, threads | The gateway process working set, managed memory, and thread count. A single increase does not establish a leak; threads do not correspond one-to-one to devices. |
| System disks | Combined capacity of all fixed host disks. Check the individual storage disk as well. |
| Runtime | Host-system uptime. Restarting the gateway process does not necessarily reset it; this is not the current Runtime process lifetime. |
| Network Interface | displays the network card name and IP address to confirm the current access address and on-site network configuration. |
- When CPU or memory remains high for a long time, first lower the debug log level, then check the collection frequency, rule flow, and forwarding target cache.
- When disk usage approaches its limit, identify files before cleanup. Preserve active databases, WAL files, and cache records awaiting replay.
- The network interface list helps confirm the IP addresses actually used by the gateway. Before modifying the network card configuration, you should prepare backup connection methods.
Trend Chart
Trend charts show recent changes in host CPU, system memory, and network upload/download speed. Resource samples refresh more frequently than the business statistics. Host traffic can include other applications and protocol overhead, so it does not directly measure point throughput.
| Chart | Explanation |
|---|---|
| CPU Trends | View CPU Usage Changes, Used to determine whether there is a sustained high load. |
| Memory Trends | View changes in memory usage to determine if there is sustained growth. |
| Network Speed | View upload and download speeds, used to assess data forwarding or changes in external access traffic. |
These are host-resource trends. Use Data Query for point history. Capacity assessment requires a sustained observation window, device and variable counts, actual request rate, and enabled workloads; see Capacity planning.
Related Links
- Collection Configuration - Channel, Device, Variable Configuration
- Real-Time Alarm - Alarm Monitoring and Handling
- System Settings - Gateway System Configuration