System
Table of Contents
- Overview
- Screen Layout — System Group
- Monitoring Screen (
/monitoring/index) - Log Screen (
/log/index) - Configuration Screen (
/config/index) - Environment Info Screen (
/env/view) - Usage Scenarios
- FAQ
- Related Screens
Overview
The System menu is an area that aggregates the operational status of the Platform itself, security accounts, configurations, logs, environment information, and clusters. The System group in the left menu currently includes the following items.
| Sub-menu | Internal URL / External Port | Purpose |
|---|---|---|
| Users | /user/index | User account management |
| Security Policy | /security/index | Password and access security policies |
| API Token | /token/index | API tokens for external integration |
| Monitoring | /monitoring/index | Real-time dashboards for infrastructure health, data pipelines, and engine metrics |
| Diagnostics | /diagnostic/index | System diagnostic event lookup |
| Logs | /log/index | Chronological lookup of server application logs (by class, method, and line) |
| Configuration | /config/index | System operational key-value configuration management (re-application/restart) |
| Environment Info | /env/view | View environment settings by property file in tabs |
| Cluster | /cluster/index | Cluster node status |
| HA | /ha/index | High Availability configuration status |
| Audit | /audit/index | Audit logs |
This document focuses on Monitoring / Logs / Configuration / Environment Info. For Users, Security, and Tokens, refer to Security Management; for Diagnostics, refer to Diagnostics; and for external tools, refer to Standards and External Tools.
Screen Layout — System Group
| Screen | Primary User | Summary |
|---|---|---|
| Monitoring | System Administrator | Infrastructure Health (5 slots) + Pipeline Diagram + Engine Metrics (9 panels) + Traffic/Cluster/Diagnostics |
| Diagnostics | Operator/Administrator | System diagnostic events and INFO/WARN/ERROR flows |
| Logs | Operator/Administrator | Detailed application logs including class, method, and line information |
| Configuration | System Administrator | Add, edit, and cache re-application of system key-value configurations |
| Environment Info | System Administrator | View property files (Engine, Application, Message Queue, Storage, Mail, WebSocket) (Read-only) |
| Cluster | System Administrator | Cluster node, mode, latency, and resource status |
| HA | System Administrator | High Availability configuration status |
| Audit | System Administrator | Audit logs |
Monitoring Screen (/monitoring/index)
Displays real-time operational metrics of the Platform in a dashboard format. The subtitle shows the server start time, allowing you to instantly verify if a restart has just occurred.
| Number | Position | Content |
|---|---|---|
| ① | Top Left | Infrastructure Health — 5 slots |
| ② | Middle Left | Data Pipeline diagram |
| ③ | Bottom Left | Engine Metrics 9-panel |
| ④ | Top Right | Data Traffic — Bytes per second + sparkline |
| ⑤ | Middle Right | Cluster — Status by node, read/write latency, storage |
| ⑥ | Bottom Right | System Diagnostics — Health timeline + recent diagnostics |
① Infrastructure Health — 5 Slots
| Slot | Label |
|---|---|
| 1 | Cache |
| 2 | MQTT |
| 3 | KAFKA |
| 4 | Event Store |
| 5 | Time Series Engine |
Each slot displays Normal/Anomaly. If all are normal, operations are in a stable state.
The subtitle lists six items: «Cache, WebSocket, MQTT, Kafka, Event Store, Time Series Engine», but only five slots are actually drawn. WebSocket/STOMP was retired in 2026-07 (browser push was replaced by SSE), and only the slot was removed first — this is a remnant of the subtitle.
② Data Pipeline Diagram
Nodes are arranged in five stages: Datasource → Message Bus → Engine → Analysis → Storage, with lines between nodes showing the actual paths.
| Stage | Node Examples |
|---|---|
| Datasource | Edge/File/API, DB, Modbus, PLC, OPC — Registered count for each node |
| Message Bus | Messaging Hub — MSG/S |
| Engine | Pipeline (Processed count, Waiting), CEP (Task count), Ingestion |
| Analysis | Scheduler, Batch, Stream (MPS) |
| Storage | Cache, Event Store, TSE (WPS) |
Small text below a node indicates its current metric. Start here when looking for blockages — if the count in a preceding stage increases while the subsequent stage remains stopped, that point is the bottleneck.
③ Engine Metrics — 9 Panels
Arranged in 3 columns × 3 rows. Each panel consists of several key-value lines and a small chart.
| Panel | Displayed Value |
|---|---|
| PPS | Current PPS, Max PPS (Collection per second, last 1 minute) |
| JVM Heap | Used, Total |
| Pipeline | Processed, Queue Waiting |
| Storage | Buffer Waiting, Active Batch |
| Messaging | KAFKA, MQTT |
| Streaming | Processed count, Timeout |
| Async Executor | Active, Waiting |
| Diagnostics | Warning, Critical |
| Cache | HIT, MISS |
④ Data Traffic
Displays bytes per second as a large number with a sparkline below it.
⑤ Cluster
| Column | Display |
|---|---|
| Status | Node status dot |
| Node IP | |
| Read | Read | Write latency (ops/s) |
| Storage | Capacity being used by the node |
Displays Total Cluster N Nodes at the top and the last update time at the bottom.
⑥ System Diagnostics
Combines a Health Timeline (with Normal, Info, Warning, Critical legends) and a list of recent diagnostics.
Each line includes the occurrence time, relative time, and a source badge (SERVER / EDGE) to immediately distinguish whether the event originated from the Platform or was uploaded from a field Edge. Detailed lookups are performed on the Diagnostics screen.
Previously, this screen had a Connection Heatmap that displayed color blocks by datasource in a grid, but it is no longer rendered (only the message text remains). To view status by connection in a grid, use the datasource card grid on the Connection Status Screen.
Log Screen (/log/index)
Provides chronological lookup of server application code-level logs (class, method, line). Unlike the diagnostic logs in /diagnostic/index, these are detailed logs used by developers/administrators for debugging.
Top Search Area
📋 로그 [기간 ▭▭▭▭] [레벨 ▼] [건수 ▼] [조회] [전체 출력] [↻]
| Control | Width | Description |
|---|---|---|
Period (search_time) | 280px | Start~End (Center aligned, Bold) |
Level (level) | 100px | All levels/INFO/WARN/ERROR |
Message (message) | 250px (Hidden by default) | Keyword search. Exposed based on operational environment |
Count (limit) | 130px | 50/100/200/300/500/1,000 |
| Search | Red + 🔍 | search() |
| Export All | Red + 📄 | downloadCSV() — Export all logs matching search criteria to CSV |
Refresh (realtime_icon) | Red + ↻ | refresh() |
The default value for the hidden field
app_nameisSERVER. This means this screen only queries server application logs.
Timeline + Quick Time Range
Same as the diagnostics screen: six quick time range buttons (10M/30M/1H/6H/12H/ALL) and a timeline (alarm_timeline).
Log Table (6 Columns)
Displays deeper code-level information than the diagnostics screen.
| Column | Width | Description |
|---|---|---|
| Level | 80px | INFO/WARN/ERROR color badge |
| Time | 160px | Log occurrence time |
| Log Class | 200px | Full Java class name |
| Method Name | 120px | Invoked method |
| Line Number | 80px | Line number in source code |
| Message | Auto | Log body + stack trace (if present) |
Log class, method, and line information are useful for system administrators to pinpoint code locations during debugging. For tracking general operational anomaly signals, the Diagnostics screen is more appropriate.
Configuration Screen (/config/index)
A screen for adding, editing, and deleting key-value configurations required for system operation and for re-applying the cache.
Address Configuration
Since the Platform cannot automatically know the address a human types into a browser, it must be entered here. It can be saved empty.
| Configuration Key | Use | If Empty |
|---|---|---|
PP_UI_CONSOLE_URL | Console address. Used in the «Go to Alarm» link in alarm emails and in QR labels | Emails are sent without the link, and QR labels do not generate a code |
PP_UI_FRONTLINE_URL | Field app address. Used in the «Open in Frontline» button on the QR public page | Hides the button |
The value must be an absolute address starting with http(s) as in https://plantpulse.example.com. Any / at the end is truncated upon saving, and requests with queries or # are rejected.
Mail server settings (MAIL_*) are also managed on this screen — Mail Settings.
Top Tools
🎚️ 시스템 설정 [설정 키 검색 ...] [조회] [↻] | [➕ 설정 추가] [🔄 재적용]
| Control | Width | Description |
|---|---|---|
Search Key (search_keyword) | 200px | placeholder: "Search configuration key ..." |
| Search | Red + 🔍 | search() — Apply keyword filter |
| Refresh | Red + ↻ | refresh() |
| Add Config | Red + ➕ | addConfig() — Open new configuration form |
| Re-apply | Blue + 🔄 | refreshCache() — Re-apply configuration cache without server restart (Tooltip: "Re-applies the configuration cache without restarting the server.") |
Configuration List Table
| Column | Width | Description |
|---|---|---|
| Configuration Key | 300px | Key recognized by the system (e.g., engine.timeout.ms) |
| Configuration Value | 600px | Current value of the key |
| Description | Auto | Memo on key purpose |
| Modified Date | 150px | Last modified time |
| Action | 80px | Edit/Delete buttons |
An information box is displayed at the bottom of the page.
ℹ️ System Configuration Guide Manages key-value settings required for system operation. Some items may require a server restart after changes.
Add/Edit Configuration Form
Navigate to the configuration form screen (/config/form) via the top Add Config button or the action buttons in the list.
| Input | Description |
|---|---|
| Configuration Key | Use only English/Numbers/./_. Example: engine.timeout.ms |
| Configuration Value | Text (Number, boolean, JSON all possible depending on key definition) |
| Description | Free text (Memo for easy operator identification) |
To apply changes immediately after saving, return to the list screen and click Re-apply. Some configurations may still require a server restart.
Environment Info Screen (/env/view)
A read-only screen for viewing property files read by the Platform during boot, organized by group tabs.
Top Information Box
❓ System Environment Information Displays environment information configured in the server system by property file. To change environment settings, modify the respective files.
- The server must be restarted after settings are changed.
6-Tab Configuration
| Tab | Display |
|---|---|
| Engine | Engine core operational settings (Time/Thread/Queue limits, etc.) |
| Application | General web application settings |
| Message Queue | Message channel connection settings (Broker host, auth, topic, etc.) |
| Storage | Time series and event store connection settings |
| SMTP settings for email sending | |
| WebSocket | Real-time push channel settings |
Table for Each Tab (Common)
| Column | Display |
|---|---|
| Key | Property key |
| Value | Current value (Masked passwords are displayed as ***) |
Values cannot be modified on the Environment Info screen. If changes are needed, the system administrator must directly modify the corresponding property file on the server and then restart the server. Key-value pairs that can be changed via the screen are managed in the Configuration screen.
Usage Scenarios
| Scenario | Screen | Procedure |
|---|---|---|
| PPS drops lower than usual | Monitoring | PPS panel chart → Infrastructure Health 5 slots → Identify bottleneck node in Data Pipeline diagram |
| Long GC / Suspected memory leak | Monitoring | GC time trend in JVM Heap panel → Notify system administrator |
| Verify normal operation after server start | Monitoring | Start time in subtitle + all 5 Infrastructure Health slots normal + Check if numbers are increasing in pipeline nodes |
| Trace ERROR in a specific class | Logs | Level=ERROR + Class name keyword in message search → Analyze logs including line numbers |
| Temporarily apply configuration change | Configuration | Add/Edit configuration → Re-apply (No restart) |
| Change password policy or session time | Environment Info | Verify current value in Application tab → System administrator modifies file → Server restart |
| Find which connection is down | Connection Management | Datasource card grid in Status Screen → Click card → Details |
FAQ
Q. How is the Monitoring screen different from the Diagnostics screen? A. Monitoring is for real-time operational metrics (throughput, memory, health) of the Platform itself, while Diagnostics is for INFO/WARN/ERROR event logs by module. Both are used by system administrators, but Monitoring answers "How is it now?" and Diagnostics answers "What happened?".
Q. One of the Infrastructure Health slots in Monitoring is red. A. The corresponding component is either unresponsive or in a failed health check state. Immediately check the SERVER or component ERROR logs on the Diagnostics screen and notify the system administrator.
Q. A node in the Data Pipeline diagram is gray. A. That stage is either not activated or has no data to process. Some stages are normally gray (e.g., backup/archiving), but if it is gray during an expected ingestion window, it may indicate a problem.
Q. I can't see the «Connection Heatmap» that used to be there.
A. It has been removed from the Monitoring screen. Connection status can be viewed in the datasource card grid on the Connection Management > Status screen; clicking a card leads to the detailed screen (/connect/view).
Q. Should I look at the Log screen or the Diagnostics screen? A. Use Diagnostics for anomaly signal tracking and Logs for code-level debugging. If an ERROR is caught in Diagnostics but the message is insufficient, check the detailed logs of that class/method in the Log screen at the same timestamp.
Q. Is the "Re-apply" button in the Configuration screen safe? A. It only refreshes the memory cache without restarting the server. It is safe for most settings, but some (such as thread pool size or DB connection pool) require a restart. If the intended behavior does not occur after re-application, contact the system administrator.
Q. I want to change the values in Environment Info from the screen. A. The Environment Info screen is read-only. Changes must be made by modifying the property files on the server and restarting. Key-value pairs that can be changed via the screen are managed in the Configuration screen.
Q. The "Export All" CSV from the Log screen is too large. A. Shorten the search period (within 1 hour) or narrow the level to ERROR/WARN before downloading again. Alternatively, use an external analysis tool after downloading the CSV.
Q. Does the Monitoring screen update automatically? A. Monitoring updates automatically via real-time push. If metrics are frozen, first check if the real-time connection status in the header is red.
Related Screens
- Dashboard — Main dashboard for operators (KPI + Right health rail)
- Diagnostics — Diagnostic logs by module
- Daily Statistics — Daily operational statistics
- Connection Management — Datasource connection status monitoring
- Status Code Definition — Infrastructure health/connection status code mapping
- Security Management — Users, policies, and API tokens