When SQL query parameters contain personal information such as resident registration numbers, phone numbers, or card numbers, the collection server detects it and stores it encrypted
Screens show masked values by default. Only users with the "View Sensitive Information" permission can see the original values, and every view of an original value is logged
AI query diagnosis receives substitute values with the same format instead of the originals. SQL error messages are also sent with personal information and secret values masked
Applies by upgrading the collection server alone, without redeploying agents
Location: Access Management → User Group Permission Management → added "View Sensitive Information Permission" type
Added a Server Groups menu that groups servers by hostname/IP rules or by direct selection. Use it where application groups cannot group servers precisely, such as in container environments
Added a Server View to the TV wallboard. It shows CPU, memory, and disk status per server group, and servers in critical or warning state can be told apart by their motion
Servers that belong to no group are collected under "No Group", so no server is left out
Location: Access Management → Server Groups / Top bar of the console → TV Wallboard → Screen Settings → View
Fixed an issue where, in a redundant collection server setup, an agent that reconnected to another server was shown as "Stopped" and its metrics were not saved even though it was running normally
Fixed an issue where data from a different date could be returned when several users queried at the same time (for example, T-Map history counts coming out lower than expected)
Fixed an issue where missing server metric values were shown as 0 % and looked normal. They are now shown as "-"