Skip to content

5.1.0-11.0

Feature Improvements​

Complete UI Redesign​

  • Redesigned almost every screen — dashboard, events, alert policies, servers, settings, and more — with a unified visual design
  • Standardized colors, spacing, font sizes, buttons, and sliders for improved readability
  • Screens with no data are now clearly distinguished from screens where collection has stopped

Two-Level Menu Restructuring​

  • Reorganized the previously long, single-row menu into two levels: top-level categories (WAS, Database, Kubernetes, SLA, Alerts, Settings) → sub-categories (Dashboard, Applications, JVM, Transactions)
  • Even when you jump directly to a deep screen via a link, the left menu automatically expands to and highlights that location
  • Each category shows a badge with its instance count next to it, which stays visible even when the menu is collapsed

Automatic Detection of 16 T-Map Incident Patterns​

  • Plots all transactions in a time window on a time (x-axis) × response time (y-axis) plane, and automatically detects the distinct shape each type of incident produces
  • The color of the status indicator circle shows severity — green (normal), yellow (minor), orange (warning), red (critical)
  • Even for the same error, guidance on where to investigate differs depending on response speed
  • The AI button next to the status circle shows, all at once: ① a one-line summary, ② the detected pattern, ③ likely causes, and ④ recommended menus to check
    • Location: WAS → T-Map

Automatic Diagnosis of 19 Transaction Root-Cause Patterns​

  • Opening an individual transaction automatically diagnoses all 19 root-cause patterns at once, ranking them by severity color (red, orange, gray) at the top of the screen
  • Automatically classifies not only slow SQL, external calls, and errors, but also easy-to-miss patterns such as N+1 repeated queries, connection pool waits, and serialized external calls
  • Slow SQL and external calls are ranked together with elapsed time and their share of the total; clicking an item jumps to its position in the timeline below

Transaction Detail Dialog and Timeline Waterfall​

  • Transaction details now open in a dialog (popup) instead of a separate page
  • The call flow is shown as a hierarchy diagram color-coded by type (database queries, external API calls, general methods, errors) alongside a timeline bar (waterfall), making it easy to spot slow segments
    • Location: WAS → Application Group / Instance / T-Map

Added Overview Tabs for Application / JVM​

  • Added an Overview tab to WAS > Application and JVM
  • Brings together 6–10 key metrics — throughput, response time, error rate, and more — on a single screen, so you can assess instance status in one click
    • Location: WAS → Application / JVM → the first "Overview" tab

Added DB Connection Usage to Reports​

  • Added a DB Connection usage item to reports, so you can also track connection pool usage trends
    • Location: Reports → Operations Report

SLA Monitoring Redesign​

  • Restructured the SLA trend screen into a summary → trend → detail flow
  • Top summary band: shows overall status, response time, success rate, and error count as color-coded blocks
  • Middle trend section: places per-service cards side by side for easy comparison, and marks when an anomaly occurred
  • Bottom error list: collapsed by default and expands only when needed; the layout adapts automatically for desktop, tablet, and mobile
    • Location: SLA Monitoring

Added AI Help Buttons to Every Chart​

  • Placed an AI help button in the same spot on every chart — metric tabs, chart headers, dashboard cards, and more — so you can check a metric's meaning and normal range right on the screen
  • The AI Performance Diagnosis button in the transaction dialog passes the same 19 automatic diagnosis results shown on screen directly to the AI, keeping what the operator sees consistent with the AI's response

Slow SQL Execution Plan Analysis and Index Recommendations​

  • When slow SQL is detected, the AI automatically provides execution plan analysis and index recommendations
  • Analysis is tailored to the database type (MySQL, Oracle, and others)

Per-Account and Per-Permission-Group Control of CogentAI​

  • CogentAI (the AI diagnosis feature) can now be turned on or off per account and per permission group, letting you enable AI features for specific groups only
    • Note: If CogentAI is disabled in a group's permissions, AI menus and buttons will not appear for users in that group. If any of your users were previously using AI features, check their group permissions.
    • Location: Settings → User Group Management
Other Improvements​
  • Improved screen rendering and the responsiveness of chart and screen transitions
  • Switched server data exchange to a WebSocket-based approach
  • Lightened screen operation in environments with a large number of monitored agents
  • Consolidated repeated alarms into a single start notification, a single recovery notification, and periodic reminders, and grouped duplicate alarms from the same cause
  • Improved alarm processing performance and stability

Bug Fixes​

  • Fixed a bug where authenticated users could not download files from the download screen

5.1.0-11.0.1​

Added Traffic Intensity Shading to T-Map​

  • Added traffic intensity shading to the transaction heatmap (T-Map), so that even within the same response-time band, periods with concentrated requests stand out by color depth, making it easy to spot traffic hotspots
    • Location: WAS → Dashboard / Application → T-Map
  • Applied by default with no extra setup required; the shading intensity can be set to strong (full saturation), medium (default), or subtle (muted)
    • Location: Top header gear icon → Preferences → Traffic Visual Intensity

Bug Fixes​

  • Removed duplicate inclusion of both minified and original UI asset files, reducing installation size and lightening screen load times
  • Fixed a bug in the T-Map detail combo box list where text was invisible due to the background color

5.1.0-11.0.2​

Enhanced T-Map Traffic Intensity Colors​

  • Adjusted the color tones for T-Map traffic intensity (strong/medium/subtle) so differences in intensity stand out more clearly
  • Aligned the shared color palette so it stays consistent with other charts

Bug Fixes​

  • Fixed a bug where agent authentication tokens were left undeleted or registered as duplicates; agent status now stays correct without manual cleanup
  • Fixed an issue where passwords could be exposed in the URL during login

5.1.0-11.0.3​

Added a Service Operations Status Screen​

  • Summarizes the status of multiple services on a single screen, letting you assess the operational state of all services at a glance
  • Displays call count, active users, error rate, TPS, average response time, and user satisfaction as time-series charts, along with changes compared to the previous day and the same day of the previous week
    • Location: Reports → Performance Analysis

View All Transactions in T-Map Detail​

  • T-Map detail can now open the full set of transactions instead of just a sample, and you can adjust the maximum number displayed at once
    • Location: WAS → T-Map → drag to select an area → Detail dialog
Other Improvements​
  • Changed T-Map error/warning cell borders to a bold solid line so they're clearly distinguished from normal cells, and adjusted the color of the top endpoint so it's no longer confused with genuinely critical ranges
  • Improved slow-query AI analysis to use tools matched to the database type, increasing analysis accuracy
  • Strengthened server cache management to improve stability during long-term operation

Bug Fixes​

  • Fixed an issue where text search did not work in T-Map detail, and a bug where the filter's regex checkbox had no effect
  • Fixed a bug where Fetch information was sometimes missing from SQL details in T-Map detail
  • Fixed a bug where no notice was shown when SQL parameters exceeded the display limit (128)
  • Fixed a bug where a system agent that was actually running normally was periodically shown as "stopped"
  • Fixed a bug where some agents were not registered to an application group on the server's first startup