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 gathers the platform's own operating status, security accounts, configuration, logs, environment information, and cluster into one area. The System group in the left menu currently contains the following items.
| Submenu | Internal URL / External Port | Purpose |
|---|---|---|
| Users | /user/index | User account management |
| Security Policy | /security/index | Password and access security policies |
| API Tokens | /token/index | API tokens for external integration |
| Monitoring | /monitoring/index | Real-time dashboard for infrastructure health, data pipeline, and engine metrics |
| Diagnostics | /diagnostic/index | View system diagnostic events |
| Logs | /log/index | View server application logs (class, method, line level) in chronological order |
| Configuration | /config/index | Manage system behavior key-value settings (reapply/restart) |
| Environment Info | /env/view | View environment settings per property file, organized by tab |
| 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 see Security Management; for diagnostics see Diagnostics; for external tools see Standards and External Tools.
Screen Layout — System Group
| Screen | Primary User | One-Line Summary |
|---|---|---|
| Monitoring | System administrator | 6-cell infrastructure health + pipeline + 6 engine metrics |
| Diagnostics | Operator/administrator | System diagnostic events and INFO/WARN/ERROR flow |
| Logs | Operator/administrator | Detailed application logs including class, method, and line information |
| Configuration | System administrator | Add, edit, and reapply cached system key-value settings |
| Environment Info | System administrator | View property files (engine/application/message queue/storage/mail/websocket) (read-only) |
| Cluster | System administrator | Cluster nodes, mode, latency, and resource status |
| HA | System administrator | High-availability configuration status |
| Audit | System administrator | Audit logs |
Monitoring Screen (/monitoring/index)
Displays the platform's own real-time operating metrics as a dashboard.
Top — Server Start Time
🩺 모니터링 YYYY-MM-DD HH:MM:SS 에 서버가 시작됨 [↻]
| Item | Display |
|---|---|
| Page title | 🩺 "Monitoring" |
| Secondary info | Server start time (small gray text) — EngineManager.getInstance().getStartedDate() |
| Refresh | Red button + ↻ — reload all metrics |
Infrastructure Health (6-Cell Panel)
The top panel is divided into six cells. Each cell has the same width (about 16.66%).
| Cell | Icon | Label | Value ID |
|---|---|---|---|
| 1 | 💾 (memory) | Cache | side_jmx_h_redis |
| 2 | 🔌 (plug) | WebSocket | side_jmx_h_stomp |
| 3 | 📡 (satellite dish) | MQTT | side_jmx_h_mqtt |
| 4 | 🌊 (stream) | KAFKA | side_jmx_h_kafka |
| 5 | 🗄️ (DB) | Event Store | (health ID — persistent event store status) |
| 6 | 🕐 (clock) | Time Series Engine | side_jmx_h_timeseries |
Each cell shows normal/abnormal status as colored text. If all are normal, operation is stable.
Data Pipeline Diagram
| Item | Description |
|---|---|
| Header | ⚡ "Data Pipeline" |
| Body | pipeline_diagram — 580px-high diagram — visualizes nodes and throughput along the ingest → validate → transform → store flow |
Throughput (events per second), queued, and dropped indicators appear above each node.
Connection Heatmap
🌐 연결 히트맵 N 에이전트
[■][■][■][■][■][■]... ← 24×24px 색 블록 그리드
─────────────────────────
🟢 정상 N 🟠 지연 N 🔴 이상 N ⬜ 미연결 N
| Item | Meaning |
|---|---|
| Header | 🌐 "Connection Heatmap " + N agents (number of registered OPC) |
| Grid body | Color block per data source (eq-block 24×24px) |
| Block hover | Tooltip with data source name and type |
| Block click | /connect/view?opc_id=... detail screen in a new window |
Color Meaning (Summary)
| Color | Meaning | ID Counter |
|---|---|---|
| 🟢 Green | Normal | heatmap_ok |
| 🟠 Orange | Delayed | heatmap_warn |
| 🔴 Red | Abnormal | heatmap_error |
| ⬜ Gray | Not connected | heatmap_unknown |
Six Engine Metric Panels
Six metric panels in a 3-column × 2-row grid. Each panel consists of a key-value table on the left and a small chart on the right/bottom.
1) PPS (Points Collected per Second · Last 1 Minute)
| Item | ID | Description |
|---|---|---|
| Current PPS | side_pps_current | Points collected per second (p/s) |
| Peak PPS | side_pps_max | Maximum over the last minute (p/s) |
| Chart | side_realtime_chart (220px) | 1-minute line chart |
2) JVM Heap
| Item | ID |
|---|---|
| Used | side_jmx_heap_used |
| Total | side_jmx_heap_total |
| GC | side_jmx_gc (milliseconds) |
| Chart | mon_jvm_chart (150px) |
3) Pipeline
| Item | ID |
|---|---|
| Tasks | side_jmx_pipe_task |
| Completed | side_jmx_pipe_processed |
| Queued | side_jmx_pipe_pending |
| Chart | mon_pipeline_chart (100px) |
4) Storage
| Item | ID |
|---|---|
| Total stored | side_jmx_store_saved |
| Writes/sec | side_jmx_store_wps |
| Buffer pending | side_jmx_store_buf |
| Active batches | side_jmx_store_batch |
| Chart | mon_storage_chart (100px) |
5) Messaging
| Item | ID |
|---|---|
| Total received | side_jmx_msg_total |
| Received per second | side_jmx_msg_rate (/s) |
| KAFKA | side_jmx_msg_kafka |
| MQTT | side_jmx_msg_mqtt |
| Chart | mon_msg_chart (100px) |
6) Streaming · Async · Diagnostics
Streaming, async executor, and diagnostic counts are displayed in a separate area of the screen (the same family of operating indicators as the Dashboard — Right Health Rail).
Log Screen (/log/index)
Shows code-level logs (class, method, line) of the server application in chronological order. Unlike the diagnostic logs of /diagnostic/index, these are detailed logs used by developers and 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. Shown depending on the operating environment |
Count (limit) | 130px | 50/100/200/300/500/1,000 |
| Search | Red + 🔍 | search() |
| Export All | Red + 📄 | downloadCSV() — export all logs matching the search criteria to CSV |
Refresh (realtime_icon) | Red + ↻ | refresh() |
The default value of the hidden field
app_nameisSERVER. That is, this screen queries server application logs only.
Timeline + Quick Time Ranges
Same six quick time range buttons (10M/30M/1H/6H/12H/ALL) and timeline (alarm_timeline) as the Diagnostics screen.
Log Table (6 Columns)
Displays one level deeper code-level information than the Diagnostics screen.
| Column | Width | Description |
|---|---|---|
| Level | 80px | INFO/WARN/ERROR color badge |
| Time | 160px | Time the log occurred |
| Log Class | 200px | Fully qualified Java class name |
| Method Name | 120px | Invoked method |
| Line Number | 80px | Line number in the source code |
| Message | Auto | Log body + stack trace (when present) |
Log class/method/line information is useful when a system administrator needs to pinpoint a code location for debugging. For tracking general operational anomaly signals, the Diagnostics screen is more appropriate.
Configuration Screen (/config/index)
A screen for adding, editing, and deleting the key-value settings that drive system behavior, and for reapplying the cache.
Top Toolbar
🎚️ 시스템 설정 [설정 키 검색 ...] [조회] [↻] | [➕ 설정 추가] [🔄 재적용]
| Control | Width | Description |
|---|---|---|
Configuration key search (search_keyword) | 200px | placeholder: "Search configuration key ..." |
| Search | Red + 🔍 | search() — apply keyword filter |
| Refresh | Red + ↻ | refresh() |
| Add Configuration | Red + ➕ | addConfig() — open the form for adding a new setting |
| Reapply | Blue + 🔄 | refreshCache() — reapply the configuration cache without restarting the server (tooltip: "Reapplies 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 | Note on the key's purpose |
| Modified | 150px | Last modification time |
| Actions | 80px | Edit and delete buttons |
An information box is displayed at the bottom of the page.
ℹ️ System Configuration Notice Manages the key-value settings required for system behavior. After changing settings, some items may require a server restart.
Add/Edit Configuration Form
Use Add Configuration at the top or an action in the list to go to the configuration form screen (/config/form).
| Field | Description |
|---|---|
| Configuration Key | Letters/digits/./_ only. Example: engine.timeout.ms |
| Configuration Value | Text (numeric, boolean, or JSON are all possible, depending on the key definition) |
| Description | Free text (a note to help operators identify the setting) |
To apply changes immediately after saving, return to the list screen and click Reapply. Some settings may require a server restart.
Environment Info Screen (/env/view)
A read-only screen for viewing the property files the platform reads at boot, organized into tabs by group.
Top Information Box
❓ System Environment Information Displays the environment information configured on the server system, per property file. To change environment settings, edit each file directly.
- The server must be restarted after settings are changed.
Six Tabs
| Tab | Contents |
|---|---|
| Engine | Engine core behavior settings (timing, threads, queue limits, etc.) |
| Application | General web application settings |
| Message Queue | Message channel connection settings (broker host, authentication, topics, etc.) |
| Storage | Time series and event store connection settings |
| SMTP settings for email delivery | |
| WebSocket | Real-time push channel settings |
Table in Each Tab (Common)
| Column | Display |
|---|---|
| Key | Property key |
| Value | Current value (masked passwords are shown as ***) |
Values cannot be edited on the Environment Info screen. If a change is required, a system administrator must edit the corresponding property file on the server directly and then restart the server.
Usage Scenarios
| Scenario | Screen | Procedure |
|---|---|---|
| PPS is lower than usual | Monitoring | PPS panel chart → 6-cell infrastructure health → identify the bottleneck node in the data pipeline diagram |
| Long GC / suspected memory leak | Monitoring | GC time trend in the JVM heap panel → notify the system administrator |
| Verify normal operation right after server start | Monitoring | Start time at top + all 6 infrastructure health cells normal + connection heatmap green |
| Track ERRORs from a specific class | Logs | Level=ERROR + class name keyword in message search → analyze logs including line numbers |
| Apply a temporary configuration change | Configuration | Add/edit setting → Reapply (no restart) |
| Change password policy or session timeout | Environment Info | Check current values in the Application tab → system administrator edits the file → restart the server |
| Identify a red block in the connection heatmap | Monitoring | Click the red block → data source detail screen opens in a new window |
FAQ
Q. How does the Monitoring screen differ from the Diagnostics screen? A. Monitoring shows the platform's own real-time operating metrics (throughput, memory, health), while Diagnostics shows INFO/WARN/ERROR event logs per module. Both are used by system administrators, but Monitoring answers "how are things right now?" and Diagnostics answers "what happened?"
Q. At least one infrastructure health cell in Monitoring is red. A. That component is not responding or its health check has failed. Immediately check the ERROR logs for SERVER or that component on the Diagnostics screen, and notify the system administrator at the same time.
Q. A node in the data pipeline diagram is gray. A. That stage is not enabled or has no data to process. Some stages are normally gray (e.g. backup and archiving); if a stage is gray during an ingest window, it may indicate a problem.
Q. One block in the connection heatmap is red.
A. The connection for that data source is in an abnormal state. Click the block to open the detail screen (/connect/view), or check the 24-hour history on the left of the Connection Management > Status screen.
Q. Should I use the Log screen or the Diagnostics screen? A. Use Diagnostics for tracking anomaly signals and Logs for code-level debugging. If Diagnostics catches an ERROR but the message is insufficient, look up the detailed logs for that class/method at the same timestamp on the Log screen.
Q. Is the "Reapply" button on the Configuration screen safe? A. It only refreshes the memory cache without restarting the server. It is safe for most settings, but some (thread pool size, DB connection pool, etc.) require a restart. If the intended behavior does not take effect after reapplying, contact your system administrator.
Q. I want to change Environment Info values from the screen. A. The Environment Info screen is read-only. Changes require editing the property file on the server and restarting the server. Key-value settings that can be changed from the UI are managed on the Configuration screen.
Q. The "Export All" CSV from the Log screen is too large. A. Narrow the search period (to within 1 hour) and restrict the level to ERROR/WARN, then download again. Alternatively, download the CSV and process it in an external analysis tool.
Q. Does the Monitoring screen refresh automatically? A. Monitoring refreshes automatically via real-time push. If the metrics are frozen, first check whether the real-time connection indicator in the header is red.
Related Screens
- Dashboard — main dashboard for operators (KPIs + right health rail)
- Diagnostics — diagnostic logs by module
- Daily Statistics — daily operating statistics
- Connection Management — data source connection status monitoring
- Status Code Definitions — infrastructure health/connection status code mapping
- Security Management — users, policies, API tokens