Release 10.1
Added Items
JMX monitoring The provider can connect to a JMX service and retrieve a set of mbeans' information. The user defines the mbean set in an mbean type filter. Different mbean sets require different filters (names).
Infrastructure Data Collector JMX The System Component discovery for Infrastructure Data Collector happens automatically when Infrastructure Data Collector starts. No input is needed from the user.
The monitoring is using Infrastructure Data Collector JMX agent. The JMX port is retrieved through the Infrastructure Data Collector bundle context.
Integration Server JMX The System Component discovery for Integration Server happens automatically with the Integration Server discovery. No additional input is needed from the user.
The monitoring is using Integration Server JMX agent. The JMX port is retrieved through the WmISExtDC package.
Integration Server “Long Running Threads” KPI This KPI counts long-running service threads in Integration Server. By default it counts service threads that are running for more than 60000 milliseconds.
UM KPI additions boolean HasQuorum - Indicates if the cluster can form a quorum.
boolean IsOnline - Indicates if the cluster is online.
MashZone NextGen Server 10.1 monitoring The following lines must be added to the wrapper.conf file.
wrapper.java.additional.200=-Dcom.sun.management.jmxremote
#wrapper.java.additional.201=-Dorg.tanukisoftware.wrapper.WrapperManager.mbean=TRUE
#wrapper.java.additional.202=-Dorg.tanukisoftware.wrapper.WrapperManager.mbean.testing=TRUE
wrapper.java.additional.203=-Dcom.sun.management.jmxremote.port=9088
wrapper.java.additional.204=-Dcom.sun.management.jmxremote.authenticate=false
wrapper.java.additional.205=-Dcom.sun.management.jmxremote.ssl=false