3DSpace Metrics

This section provides all metrics consumed by the standard JMX-capable monitoring agents for 3DSpace services.

Your monitoring solution or the tool (for example, IBM Tivoli Server or Nagios) used to collect monitoring information on the operating system, application server, database needs to be configured to collect these metrics. The tables below describe the different metrics for each service.

This page discusses:

MCS Metrics: Status
MCS Metrics: Memory
MCS Metrics: Database
MCS Metrics: Settings

See Also

Activating Publication of MCS Events as Strongly-typed MBeans

MCS Metrics: Status


Metric Name	Unit	Description
startDate	Seconds	Date the server was started (number of seconds since 00:00:00 UTC, January 1, 1970)
uptime	Seconds	Amount of time the server has been running
nbExceptions	Count	Number of exceptions encountered. This count only includes exceptions returned by the kernel when a Studio Customization Toolkit call is performed. This count does not include other types of exceptions.

MCS Metrics: Memory


Metric Name	Unit	Description
memory.kernel.highwater	bytes	Amount of highwater memory bytes
memory.kernel.allocatedBytes	bytes	Amount of memory bytes allocated in the given number of allocated blocks
memory.kernel.allocatedBlocks	N/A	Amount of allocated blocks
memory.kernel.reservedBytes	bytes	Amount of reserved memory bytes
memory.kernel.reservedBlocks	N/A	Amount of reserved blocks

MCS Metrics: Database


Metric Name	Unit	Description
db.connection.nbConnections	Count	Number of database connections
db.connection.nbDisconnections	Count	Number of database disconnections
db.connection.nbExceedConnections	Count	Number of database connections exceeding the size of the database connection pool. The connection pool is determined by the MX_CONNECTION_POOL_SIZE setting for the Live Collaboration Server.
db.sql.statement.nbExecuted	Count	Number of SQL statements executed
db.sql.statement.nbParsed	Count	Number of SQL statements parsed

MCS Metrics: Settings


Metric Name	Instance	Unit	Description
settings.system.memoryLimit	instance=mcs \| mcsForBatches	bytes	High water mark of allowable memory allocation for the native Live Collaboration Server kernel. This value is the same as MX_MEMORY_SYSTEM_LIMIT, see the "Memory variables" section of the Live Collaboration Server Administration Guide.
settings.system.cacheLimit	instance=mcs \| mcsForBatches	bytes	Threshold on memory consumption for all threads, before using the database.