r5 - 2020-06-02 - 15:24:07 - TimFeeneyYou are here: TWiki >  Deployment Web > DeploymentMonitoring > CLMServerMonitoring > CLMServerMonitoringDataDictionary > CLMServerMonitoringMonitor

CLM Server Monitoring - Smarter Server Monitor (DEPRECATED: CLM Server Monitoring is no longer supported and was dropped in version 6.0.3.)

Authors: JorgeAlbertoDiaz
Build basis: Collaborative Lifecycle Management 4.0.4

The CLM Server Monitoring Smarter Server monitor provides management attributes and operations for all the registered individual monitors.

JMX Interface Name: com.ibm.team.server.monitoring.jmx.SmarterServerMonitorMBean
JMX Object Name: team.server.<application public URI context>@<port>:type=SmarterServer
JMX Object Name Example: team.server./jts@9443:type=SmarterServer

This object doesn't provide resources monitoring itself, nor exposes management attributes. A child MBean is registered providing the configuration options for the monitors.

Monitor Attributes

This monitor object does not expose management attributes.

Monitor Operations

JMX Operation Signature Return Type Description
dismissAllProblems() void When called, all the problems tracked by all the monitors are dismissed

Child MBeans

This section gathers information regarding MBeans that are contained within this monitor

Configuration object

A configuration object provides management information for the individual monitors. Just one object of this type will be created and registered for each application monitored by CLM Server Monitoring.

JMX Interface Name: com.ibm.team.server.monitoring.jmx.beans.SmarterServerConfigurationMBean
JMX Object Name: team.server.<application public URI context>@<port>:type=SmarterServer,name=Configuration
JMX Object Name Example: team.server./jts@9443:type=SmarterServer,name=Configuration

Attributes

The following categories of management attributes are exposed by this JMX object:

  • Monitors management attributes: allowing for central administration (enablement and threshold set), of the individual CLM Server Monitoring monitors. Modifying the value of these attributes change the associated ones in the individual monitor objects. This type of attributes are expected to be removed in a following release, so each monitor will be responsible for managing its own configuration information.
  • CLM Server Monitoring configuration attributes: that allow to set specific configuration options for the CLM Server Monitoring solution itself

JMX Attribute JMX Type Is Writeable? Default Value Description
AllMonitorsEnabled boolean Yes false This attribute enables/disables all the individual CLM Server Monitoring monitors. Modifying the value of this attribute will change the "Enabled" attribute value in the individual monitors, but it won't modify the value of the rest of management attributes contained in this JMX Object
CORBAMonitorEnabled boolean Yes false Whether the CORBA Monitor is enabled. See CORBA Monitor for specific information
CORBAMonitorThreshold long Yes 10000 Threshold value for the CORBA Monitor
CacheDiskStoreDirectory String No Application server temporary folder Disk storage location of the CLM Server Monitoring cache
CacheMaxBytesLocalDisk String Yes 10G Number of bytes that CLM Server Monitoring cache will occupy on the local disk. The value may be a percentage or the actual number of bytes in the form: 10G or 10M. When the cache will be offloaded to local disk depend on the value of "!CacheMaxEntriesLocalHeap" attribute
CacheMaxEntriesLocalHeap long Yes 30000 Number of bytes on the local heap the CLM Server Monitoring cache will occupy. Once this max is reached the cache will be offloaded to disk. The value may be a percentage of the heap space or the actual number of bytes such as: 10M or 10G
CacheMonitorEnabled boolean Yes false Whether the Cache Monitor is enabled. See Cache Monitor for specific information
CacheMonitorThreshold long Yes 10000 Threshold value for the Cache Monitor
CachingEnabled boolean Yes true Whether CLM Server Monitoring cache is enabled
DiagnosticsEnabled boolean Yes false Whether the server diagnostics JMX management interface is enabled
HttpClientMonitorEnabled boolean Yes false Whether the HTTP Client Monitor is enabled. See HTTP Client Monitor for specific information
HttpClientMonitorThreshold long Yes 10000 Threshold value for the HTTP Client Monitor
JNDIMonitorEnabled boolean Yes false NA. Monitor not supported
JNDIMonitorThreshold long Yes 10000 NA. Monitor not supported
JenaMonitorEnabled boolean Yes false Whether the Jena Monitor is enabled. See Jena Monitor for specific information
JenaMonitorThreshold long Yes 10000 Threshold value for the Jena Monitor
PoolMonitorEnabled boolean Yes false Whether the Pool Monitor is enabled. See Pool Monitor for specific information
PoolMonitorThreshold long Yes 10000 Threshold value for the Pool Monitor
RequestMonitorEnabled boolean Yes false Whether the Request Monitor is enabled. See Request Monitor for specific information
RequestMonitorThreshold long Yes 10000 Threshold value for the Request Monitor
SQLMonitorEnabled boolean Yes false Whether the DB Statement Monitor is enabled. See DB Statement Monitor for specific information
SQLMonitorThreshold long Yes 10000 Threshold value for the DB Statement Monitor
ServiceMonitorEnabled boolean Yes false Whether the Service Monitor is enabled. See Service Monitor for specific information
ServiceMonitorThreshold long Yes 10000 Threshold value for the Service Monitor
SystemMonitorEnabled boolean Yes false Whether the JVM Monitor is enabled. See JVM Monitor for specific information

Operations

This object does not expose management operations.

External links:

Additional contributors: TWikiUser, TWikiUser

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r5 < r4 < r3 < r2 < r1 | More topic actions
Deployment.CLMServerMonitoringMonitor moved from Deployment.SmarterServerMonitor on 2013-08-06 - 21:42 by Main.geraldmi -
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.