Monitoring Requirement for v3.1

MON01 P1 Monitoring at Cluster level with drill-down capabaility to point to the real issue
MON02 P1 Good UI for the monitoring value-adds
MON03 P1 Fix performance issues
MON04 P1 Improve number of probes

Monitoring Requirement for V3

AdminConsole-008 P1 Provide a 'dashboard' view of application clusters and/or instances. With one quick view an administrator should be able to see the status of an installation.
AdminConsole-016 P3 Live update of monitoring statistics from within admin UI (Community Request).
EU7 P2 Improved monitoring support. Instead of dumping the raw data, it is better to interpret and provide the analysed data Root cause analysis coupled with self-management.
INT P2 Improved monitoring UI with overall system health  
INT P2 Root Cause Analysis  
INT P2 Resources Monitoring Refer to IEC slides
INT P2 MQ Monitoring Refer to IEC slides
INT P2 JDBC Monitoring Improve presentation from numbers to charts, snapshots.
INT P2 JVM Monitoring Integrate JConsole type of monitoring through admin-console
INT P1 Applications Monitoring Active Sessions, Performance, Processing Time, Call Flow
INT P1 Resources Monitoring JDBC Connection Pool/Datasource Call Flow Monitoring
INT P1 Log Statistics Monitoring Display Graphs Based on Message Filtering, show messages, and possible root cause analysis
INT P3 Transactions UI Need to see whether we have is sufficient
INT P1 Intance/Cluster Monitoring Color coded status to show the health of an instance/cluster, Diagnose information to display threshold limitations of memory, cpu usage etc.
INT P1 Third party monitoring framework Evaluate existing monitoring framework like QUEST, WILEY etc. tightly integrate the popular ones with GF V3
HS P2 Allow setting of alerts and bounds per application For e.g " set maximum time for response for application A as 30 ms". If App A goes over 30 ms about x% time send an alert to the administrator
HS P2 Classify application zones/support level E.g Application A, B, C. A is in Platinum zone, B is in Gold zone and C is in Silver. If there is a resource crunch, application A gets serviced over B and C.
HS P3 SMS alerts if server crashes Should help administrators in mission critical sites
INT P2 Tivoli's support for JMX We may be able to get help from ISV engineering here
INT P3 Netcool's support for JMX Explore