Skip to Content
Documentation07 · AdministrationSystem overview
On this page

System Overview

Open System Overview to inspect collection devices, variables, alarms and forwarding targets, then use the connection topology to locate the current gateway and its connected objects. Wait for loading to finish and compare successive samples before judging the current state.

Inspect the running gateway

First Look at Terms

TermsOn-site Understanding
ChannelsCommunication links from gateways to field devices, such as a TCP connection, a serial port, or a listening port.
Devicea PLC, instrument, acquisition module, or a logic acquisition object managed by plugins.
VariableA point in the point list, such as temperature, pressure, operating status, fault state, or control write point.
Real-time alarmsAlarm events that still require attention.
CPU/memory/diskgateway 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 signing in, open System Overview from the main navigation.

Current system overview with business statistics and connection topology

Statistics Card

CardDescription
Collection devicesCompare the configured total with the online count. Inspect offline devices in Collection Configuration.
Total number of variablesDisplays the total number of variables and indicates the number of normal variables.
Real-time AlarmShows alarm-variable and event counts requiring attention.
Forwarding targetsCompare total and online targets, then verify their actual output at the receiver.

If statistics or sections are missing, check viewing permissions and loading state. — means data is unavailable or not yet loaded. A failed refresh can retain the last successful value, so check status and collection time. 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.

Check collection readings

  1. Open a known collection point and compare its value, raw value, quality, and advancing collection time with the source.
  2. Check the associated device plugin, execution interval, and channel endpoint, then test the actual protocol address.
  3. In a permitted test environment, stop the source and inspect device and variable offline states and the last collection time.
  4. Restart the same source without recreating the channel, device, or variable. Verify restored quality and advancing time.
  5. If forwarding is configured, verify a new message at an independent receiver. See Collection debugging.

Page Layout

The overview shows business statistics and the connection topology, with sections adapting to the available width. Open System Management for project settings and System Monitor for process, memory, and hardware diagnostics.

The canvas connects southbound collection devices, the gateway, and northbound forwarding targets.

  1. Search by device, channel, target, or plugin name and optionally filter online, offline, disabled, or standby objects.
  2. Drag the canvas and use zoom, fit, or gateway-location controls. Ctrl / Command plus the wheel also zooms.
  3. Select a node on the canvas or in the node selector. Check its identity and actual runtime state, then inspect configuration or logs.
  4. Clear search and state filters and refresh to check the complete permitted scope.

The topology includes only objects the account may view. If an object is missing, check viewing permissions, search terms, and state filters.

Inspect project details

Open System Management → System Settings to inspect the loaded project and gateway settings. Check the software version, gateway identity, and licensed resource limits in their corresponding system or licensing pages. These details are separate from the overview’s online counts.

Monitor system resources

System Resource Monitoring

Open System Management → System Monitor for process, thread-pool, GC, and memory trends. Overview summaries depend on the layout; use System Monitoring and Memory Analysis for detailed measurements and operations.

MetricsDescription
CPU UsageSystem CPU Usage Percentage. If the rate remains high, prioritize high-frequency collection, rule processes, and data forwarding.
Memory usageSystem memory usage percentage. If persistently high, check the number of variables, cache queues, and runlogs.
Disk UsageUsed and total capacity of the disk containing the gateway program. Insufficient space can affect history, cache files, and logs.
Process memory, GC memoryThe gateway process working set and managed memory.
System disksCombined capacity of all fixed host disks. Check the individual storage disk as well.
RuntimeHost-system uptime. View gateway process uptime in System Monitor.
Network Interfacedisplays the network card name and IP address to confirm the current access address and on-site network configuration.

When disk usage approaches its limit, identify files before cleanup. Preserve active databases, WAL files, and cache records awaiting replay.

Trend Chart

Open System Monitor for recent changes in host CPU, system memory and network upload/download speed. Host traffic can include other applications and protocol overhead, so it does not directly measure point throughput.

ChartExplanation
CPU TrendsView CPU Usage Changes, Used to determine whether there is a sustained high load.
Memory TrendsView changes in memory usage to determine if there is sustained growth.
Network SpeedView 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.