EditAttachPrintable
r5 - 2018-07-18 - 06:55:06 - RichardWattsYou are here: TWiki >  Deployment Web > DeploymentMonitoring > CLM605MXBeans > Common605Beans

Common Managed Beans todo.png

Authors: Richard Watts, Vishwanath Ramaswamy, Vaughn Rokosz
Build basis: CLM 6.0.5



This page is under construction




Introduction


The Common Managed Beans that were introduced in 6.0.5. They are grouped into four categories, Cluster, Performance, Server Health and Usage Metrics. From there, they are further categorized by background task.


Table 1 - Categories


Category Description Background Tasks
Usage Metrics The Usage Metrics category CommonMetricsCollectorTask
ProjectMetricsCollectorTask
LicenseMetricsCollectorTask
Cluster Metrics Rational Team Concert supports being deployed clustered. Clustered Metrics are only available in a CLM Instance where you are using clustering. If you enable cluster metrics without deploying clustering, you will not see any clustered related values. CommonMetricsCollectorTask
ClusterMetricsTask
Performance Metrics The Performance metrics category covers collecting metrics related to overall system performance from users, services, data or database loads. MetricsCollectorTask
HighFrequencyMetricsNodeScopedTask
FullTextIndexDataCollectorTask
IndexDataCollectorTask
ItemCountMetricsCollectorTask
SQLActivityMetricsTask
Server Health Metrics Server Health Metrics covers important mbeans that ensure your system is up and running (diagnostics) and data integrity (online verify). DiagnosticsMetricsTask
MetricsCollectorTask
OnlineVerifyMetricsTask


Background tasks are the mechanism we use to populate the managed beans. These are enabled in Advanced properties. Changing the interval of a background task will only go into effect after the next interval or when the application is restarted.


Table 2 - Background Tasks


Background Task Description Managed Beans
LicenseMetricsCollectorTask   Floating license consumption statistics – Concurrent use
Floating license consumption statistics – Concurrent use
Floating license consumption statistics – License checkout time
Floating license consumption statistics – License Denials
Token License consumption statistics – Concurrent use
Token License consumption statistics – License Denials
Compatible Client Login Details – Number of logins
CommonMetricsCollectorTask   Cluster Member Information
ClusterMetricsTask   MQTT Endpoint Metrics
MQTT Memory Metrics
MQTT Store Metrics
MQTT Topic Metrics
Jazz MQTT Service – Messages Received Count
Jazz MQTT Service – Messages Received Frequency (msgs/sec)
Jazz MQTT Service – Messages Received Reset Counter
Jazz MQTT Service – Messages Sent Count
Jazz MQTT Service – Messages Sent Frequency (msgs/sec)
Jazz MQTT Service – Messages Sent Reset Counter
Jazz MQTT Service – Messages Sent Queued Counter
Jazz MQTT Service – Messages Received Queue Exhausted Counter
Jazz MQTT Service – Published Messages Lost Count
Jazz MQTT Service – Message Processing Time
Jazz MQTT Service – Message Sent Result - Success
Jazz MQTT Service – Message Sent Result - Failure
Jazz MQTT Service – Message processed on main thread
Jazz MQTT Service – Received Messages - Queue Size
Jazz MQTT Service – Received Messages – thread pool size
Jazz MQTT Service – Failed connections to broker
Jazz MQTT Service – Lost connections to broker
Distributed Data Microservice – Key Size
Distributed Data Microservice – Added Value Size
Distributed Data Microservice – Number of Elements in Map
Distributed Data Microservice – Bytes transferred (in kb)
Distributed Data Microservice – Elapsed time (in ms)
MetricsCollectorTask   Active Services
Asynchronous Tasks Elapsed Time
Asynchronous Tasks Queued Count
Expensive Scenario Details
JDBC Connection Pool Active Connections
JDBC Connection Pool Queue Length
JDBC Connection Pool Usage Percentage
JDBC Connection Pool Wait Time in milliseconds
RDB Mediator Connection Pool Active Connections
RDB Mediator Connection Pool Queue Length
RDB Mediator Pool Usage Percentage
RDB Mediator Pool Wait Time in milliseconds
Local configuration management cache statistics – Cache hit ratio
Local configuration management cache statistics – Entry added to cache
Local configuration management cache statistics – Entry found in cache
Local configuration management cache statistics – Entry not found in cache
Local configuration management cache statistics – Entry removed from cache
Local configuration management cache statistics – Entry replaced in cache
Local configuration management cache statistics – Entry garbage collected from cache
Local configuration management cache statistics – Time for computing a value in ms
Local configuration management service statistics – Elapsed time in milliseconds
Local configuration management service statistics – Creation time in milliseconds
Local configuration management service statistics – Rows created in in a new stream
Transaction cache statistics – Number of hits
Transaction cache statistics – Number of misses
Transaction cache statistics – Number of invalidations
Transaction cache statistics – Number of entries added
Transaction cache statistics – Number of entries auto updated
Resource Intensive Scenarios – Elapsed time in milliseconds
Resource Intensive Scenarios – Summary Elapsed time in milliseconds
Web Service Statistics – Elapsed time in seconds
Web Service Statistics – Bytes sent to client
Web Service Statistics – Bytes received from client
Web Services Statistics Summary Over Collection Intervals
HighFrequencyMetricsNodeScopedTask   Active Services Summary
FullTextIndexDataCollectorTask   Full Text Index Information
IndexDataCollectorTask   JFS Index Information
ItemCountMetricsCollectorTask   Item Count Details
SQLActivityMetricsTask   SQL Activity
SQL Activity Summary
DiagnosticsMetricsTask   Diagnostics
MetricsCollectorTask   Log Events
Server Information
OnlineVerifyMetricsTask   Repotools Verify Information
CommonMetricsCollectorTask   Contributor Information
Project Area Summary Information
ProjectMetricsCollectorTask   Project Area Information
Work Item Information


Table 3 - Managed Beans


MBean Name Object Name Description Frequency
Distributed Data Microservice – Elapsed time (in ms) com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, Distributed Persistence Layer,facet=Elapsed time (in ms),counterName=* This facet reports the times it takes for the data transfers to and from the persistence layer. 15m
Active Services com.ibm.team.foundation.activeservices:name=<< contextRoot>>, type=activeServicesMetrics, serviceName=* This is all the active services currently running in the server. Each service provides information like service name, requested user, start time and duration, and start time. This is useful to understand the standard patterns of low level service activity in a production system. Helps to understand the unique set of users currently working in the system. 15m
Active Services Summary com.ibm.team.foundation.activeservices:name=<< contextRoot>>, type=activeServicesSummaryMetrics This is a summary of the total count of active services running in the system. This provides information like total count, CPU ratio and services that have exceeded duration thresholds. This is useful to understand the active services that are long running. Helps also to understand if the system specifications are adequate to meet the user load. 15m
Contributor Information com.ibm.team.foundation.contributors:name=<< contextRoot>>, type=contributorMetrics This publishes the number of active and archived users in the repository. This is useful to understand the active registered users. 60m
Diagnostics com.ibm.team.foundation.diagnostic:name=<< contextRoot>>, type=diagnosticMetrics, testId=* This provides the results of the server diagnostics which by default runs every hour. This is useful to track the status of the periodic execution of server diagnostics. 70m
Log Events com.ibm.team.foundation.logevents:name=<< contextRoot>>, type=logEventDetailsMetrics, errorNameAndId=* This provides all the errors and warnings from the log files and for each log entry provides additional contextual information like userd id, active configuration, servlet request URL etc. This is useful to understand error log entries occurring in the system when other aspects of the system are misbehaving. This provides a maximum of 1000 entries during the collection interval. 15m
Full Text Index Information com.ibm.team.foundation.fulltextindexing:name=<< contextRoot>>, type=richTextIndexDataMetrics This provides the index size and index location information for the full text lucene index used by RTC and RQM. This is useful to track the size of the lucene index. 60m
JFS Index Information com.ibm.team.foundation.jfsindexing:name=<< contextRoot>>, type=jfsIndexDataMetrics, indexname=* This provides the index size and index queue information for the rdf and text index used by DNG and DM. Index information is provided for RDF Live, RDF History, Text Live and Text History indices. This is useful to track the size of the index and indirectly help with determining the optimal RAM and JVM Heap memory for the system. 60m
Item Count Details com.ibm.team.foundation.itemcounts:name=<< contextRoot>>, type=itemCountMetrics,type Name=* This provides information about each type of item in the repository and their counts in terms of number of states and the overall size of these items in relation to the total size. This is useful to understand the data growth in the system and also the breakdown between the different types of items. Sometimes items like attachments or build results may be growing at an alarming rate and tracking this metric can explain the reason for this growth. Added to this, increase in DB size during a period can also be explained by the items that were added during this period. 1 week
Repotools Verify Information com.ibm.team.foundation.datavalidation:name=<< contextRoot>>, type=onlineVerifyMetrics, componentId=* This provides the results of the repository verifiers, which are used in the verify repotools infrastructure. This is useful to keep an eye on the data integrity of the production database. This is useful to track the status of the periodic execution of data verification rules against the repository. 1 week
Project Area Information com.ibm.team.foundation.projectarea:name=<< contextRoot>>, type=projectMetrics, projectNameAndId=* This publishes the number of contributor, team, development lines, work items and attachments for each project area in the repository. Additionally it indicates if the project is archived or not. You can monitor these and also setup alerts if the usage patterns are not within normal parameters. In future it will contain an attribute for the total size of the project area in the repository. This will help determine if the project warrants its own server and can be a candidate for server split. It also provides if the project area has be opted in and provides configuration management metrics like number of component, streams, baselines etc. 1 week
Project Area Summary Information com.ibm.team.foundation.projectarea:name=<< contextRoot>>, type=projectSummaryMetrics This publishes the number of projects in the repository and if they are archived or not. 60m
Expensive Scenario Details com.ibm.team.foundation.scenarios:name=<< contextRoot>>, type=expensiveScenarioDetailsMetrics, scenarioNameAndId=* This will publish details about the active and completed resource intensive scenarios in the system. This is useful to understand how the resource intensive scenarios are performing and understand what are the active scenarios at any given point in time. It also gives details about the user who requested the scenario. 15m
Server Information com.ibm.team.foundation.server:name=<< contextRoot>>, type=serverMetrics This publishes the server health information including memory usage, DB ping time and status on services and DB connections. This is useful to understand how the server is performing. Most important attribute is the dbPingTime. If the latency between server and DB gets worse it will impact the almost every use case in the product. 15m
SQL Activity com.ibm.team.foundation.sqlactivity:name=<< contextRoot>>, type=sqlActivityMetrics, id=* This provides the SQL activity during the specified interval as a MBean. This is useful to understand the standard patterns of SQL activity in a production system. This is useful to track the counts and average response times for many SQL queries. Helps to understand the high runners and optimize them. Also helps to drive data partitioning decisions and preserve the query response time. 60m
SQL Activity Summary com.ibm.team.foundation.sqlactivity:name=<< contextRoot>>, type=sqlActivitySummaryMetrics, sqlStmtType=* This provides the summary SQL activity during the specified interval as a MBean. This is useful to understand the standard patterns of SQL activity in a production system. This is useful to track the counts and average response times for many SQL queries by type. Helps to understand the high runners and optimize them. Also helps to drive data partitioning decisions and preserve the query response time. 60m
Work Item Information com.ibm.team.foundation.projectarea:name=<< contextRoot>>, type=projectWorkItemMetrics, typeNameAndProjectNameAndId=* This provides the type of workitem and the total count of this type of work items for each project area. 1 week
Cluster Member Information com.ibm.team.foundation.clustermembers:name=<< contextRoot>>, type=clusterMemberDataMetrics, nodeId=* This publishes the basic node information for each node in the cluster and also the node state. 60m
MQTT Endpoint Metrics com.ibm.team.foundation.cluster.mqtt:name=<< contextRoot>>, type=mqttEndpointStatistics This provides information about configured end points with the MessageSight MQTT broker. It has details like total connections, bytes read or written, messages sent/received/lost etc. 15m
MQTT Memory Metrics com.ibm.team.foundation.cluster.mqtt:name=<< contextRoot>>, type=mqttMemorytatistics This provides information about the memory characteristics of the MessageSight MQTT broker machine. It includes details like free memory, message payloads etc. 15m
MQTT Store Metrics com.ibm.team.foundation.cluster.mqtt:name=<< contextRoot>>, type=mqttStoretatistics This provides information about the disk and pool characteristics of the MessageSight MQTT broker machine. 15m
MQTT Topic Metrics com.ibm.team.foundation.cluster.mqtt:name=<< contextRoot>>, type=mqttTopictatistics This provides information about the topics in the MessageSight MQTT broker machine. It includes details like subscriptions, published messages etc. 15m
Asynchronous Tasks Elapsed Time com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=asynchronoustasks,facet=elapsed time in seconds, counterName=* This is useful to track the average response time for background tasks and help with tuning the frequency of these and also monitor the degradation in their response time. 15m
Asynchronous Tasks Queued Count com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=asynchronoustasks, facet=queuedcount, counterName=* This is useful to track the backlog of the background tasks being queued up. 15m
JDBC Connection Pool Active Connections com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=resourceusage, facet=activeconnections, counterName= JDBC connection pool This is useful to understand the sizing for the JDBC pools and if these pool sizes are correctly set for the current concurrency level of the system. If the size is small then higher concurrency will result in operations waiting and is the size is too big then system resources are consumed even though the load does not exist (Article). The different facets are active connections, usage percentage, queue length and wait time. 15m
JDBC Connection Pool Queue Length com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=resourceusage, facet=queuelength, counterName=JDBC connection pool This is useful to understand the sizing for the JDBC pools and if these pool sizes are correctly set for the current concurrency level of the system. This facet highlights the size of the queue of pending connection requests. 15m
JDBC Connection Pool Usage Percentage com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=resourceusage, facet=usagepercentage, counterName=JDBC connection pool This is useful to understand the sizing for the JDBC pools and if these pool sizes are correctly set for the current concurrency level of the system. If the size is small then higher concurrency will result in operations waiting and is the size is too big then system resources are consumed even though the load does not exist (Article). The different facets are active connections, usage percentage, queue length and wait time. 15m
JDBC Connection Pool Wait Time in milliseconds com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=resourceusage, facet=wait time in ms, counterName=JDBC connection pool This is useful to understand the sizing for the JDBC pools and if these pool sizes are correctly set for the current concurrency level of the system. This facet highlights the size of the queue of pending connection requests. 15m
RDB Mediator Connection Pool Active Connections com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=resourceusage, facet=active connections, counterName=RDB mediator pool This is useful to understand the sizing for the RDB mediator pools and if these pool sizes are correctly set for the current concurrency level of the system. If the size is small then higher concurrency will result in operations waiting and is the size is too big then system resources are consumed even though the load does not exist (Article). The different facets are active connections, usage percentage, queue length and wait time. 15m
RDB Mediator Connection Pool Queue Length com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=resourceusage, facet=queue length,counterName=RDB mediator pool This is useful to understand the sizing for the RDB mediator pools and if these pool sizes are correctly set for the current concurrency level of the system. This facet highlights the size of the queue of pending connection requests. 15m
RDB Mediator Pool Usage Percentage com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=resource usage,facet=usage percentage,counterName=RDB mediator pool This is useful to understand the sizing for the RDB mediator pools and if these pool sizes are correctly set for the current concurrency level of the system. If the size is small then higher concurrency will result in operations waiting and is the size is too big then system resources are consumed even though the load does not exist (Article). The different facets are active connections, usage percentage, queue length and wait time. 15m
RDB Mediator Pool Wait Time in milliseconds com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=resource usage,facet=wait time in ms,counterName=RDB mediator pool This is useful to understand the sizing for the RDB mediator pools and if these pool sizes are correctly set for the current concurrency level of the system. This facet highlights the size of the queue of pending connection requests. 15m
Local configuration management cache statistics – Cache hit ratio com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=local config mgmt cache statistics,facet=Cache hit ratio as a percentage,counterName=* This is useful to understand how the caches are performing. In a production environment the hit ratio of the caches should be greater than 95% (Blog). Other facets are Entry added to cache, Entry removed from cache, Entry found in cache, Entry not found in cache, Entry replaced in cache and Entry garbage collected from cache. 15m
Local configuration management cache statistics – Entry added to cache com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=local config mgmt cache statistics,facet=Entry added to cache,counterName=* This is useful to understand how the caches are performing. In a production environment the hit ratio of the caches should be greater than 95% (Blog). This facet highlights the entries added to the cache 15m
Local configuration management cache statistics – Entry found in cache com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=local config mgmt cache statistics,facet=Entry found in cache,counterName=* This is useful to understand how the caches are performing. In a production environment the hit ratio of the caches should be greater than 95% (Blog). This facet highlights the entries found in cache 15m
Local configuration management cache statistics – Entry not found in cache com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=local config mgmt cache statistics,facet=Entry not found in cache,counterName=* This is useful to understand how the caches are performing. In a production environment the hit ratio of the caches should be greater than 95% (Blog). This facet highlights the entries not found in cache 15m
Local configuration management cache statistics – Entry removed from cache com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=local config mgmt cache statistics,facet=Entry removed from cache,counterName=* This is useful to understand how the caches are performing. In a production environment the hit ratio of the caches should be greater than 95% (Blog). This facet highlights the entries removed from cache 15m
Local configuration management cache statistics – Entry replaced in cache com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=local config mgmt cache statistics,facet=Entry replaced in cache,counterName=* This is useful to understand how the caches are performing. In a production environment the hit ratio of the caches should be greater than 95% (Blog). This facet highlights the entries replaced in cache 15m
Local configuration management cache statistics – Entry garbage collected from cache com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=local config mgmt cache statistics,facet=Entry garbage collected from cache,counterName=* This is useful to understand how the caches are performing. In a production environment the hit ratio of the caches should be greater than 95% (Blog). This facet highlights the entries garbage collected from cache. 15m
Local configuration management cache statistics – Time for computing a value in ms com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=local config mgmt cache statistics,facet=Time for computing a value in ms,counterName=* This is useful to understand how the caches are performing. In a production environment the hit ratio of the caches should be greater than 95% (Blog). This facet highlights the average time to compute a value in ms. 15m
Local configuration management service statistics – Elapsed time in milliseconds com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=local config mgmt service,facet=Elapsed time (in ms),counterName=* This helps with monitoring the average execution time of the different local configuration management service API for DNG and DM. This includes but not limited to operations like creating a changeset, creating a stream, creating a baseline, committing a changeset etc. 15m
Local configuration management service statistics – Creation time in milliseconds com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=Configuration aware functionality,facet=Creation time (ms),counterName=* This helps with monitoring the average execution time of some of the advanced config mgmt. operations like skew detection on streams and baselines. 15m
Local configuration management service statistics – Rows created in in a new stream com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=Configuration aware functionality,facet=Rows created,counterName=* This helps with monitoring the number of rows created when a steam create operation is executed. 15m
Transaction cache statistics – Number of hits com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=Item Cache Summary,facet=hits,counter Name=* This provides the transaction cache(s) operation metrics. This provides counts for the following operations on ITEM currents and ITEM state caches. The facets are added, misses, invalidated, hits and autoupdated. This is useful to understand how the caches are performing. In a production environment the hit ratio of the caches should be greater than 95% (Blog). 15m
Transaction cache statistics – Number of misses com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=Item Cache Summary,facet=misses,counterName=* This provides the transaction cache(s) operation metrics. This provides counts for the following operations on ITEM currents and ITEM state caches. This facet highlights the number of misses from the cache. 15m
Transaction cache statistics – Number of invalidations com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=Item Cache Summary,facet=invalidated, counterName=* This provides the transaction cache(s) operation metrics. This provides counts for the following operations on ITEM currents and ITEM state caches. This facet highlights the number of invalidations from the cache. 15m
Transaction cache statistics – Number of entries added com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=Item Cache Summary,facet=added,counterName=* This provides the transaction cache(s) operation metrics. This provides counts for the following operations on ITEM currents and ITEM state caches. This facet highlights the number of entries added to the cache. 15m
Transaction cache statistics – Number of entries auto updated com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=Item Cache Summary,facet=autoUpdated ,counterName=* This provides the transaction cache(s) operation metrics. This provides counts for the following operations on ITEM currents and ITEM state caches. This facet highlights the number of entires that were updated in the cache. 15m
Resource Intensive Scenarios – Elapsed time in milliseconds com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=scenarios,facet=elapsed time in millisecs,counterName=* This provides the counts and average response time for each of the resource intensive scenarios in the system (Deployment Wiki). This is useful to understand how the resource intensive scenarios are performing and track any degradation in their response times. 15m
Resource Intensive Scenarios – Summary Elapsed time in milliseconds com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=scenarios,facet=elapsed time in millisecs,counterNameAndId =summary_* This provides the counts and average response time for all the resource intensive scenarios in the system (Deployment Wiki) during the collection interval. This is useful to understand how the resource intensive scenarios are performing and track any degradation in their response times. 15m
Web Service Statistics – Elapsed time in seconds com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=web service,facet=elapsed time in secs,counterName=* This is useful to track the average response time for web services and watch for degradations. Added to this the other facets are bytes sent to client and bytes received from client. These are useful to track the average request pay load and response pay load for web services and watch for large payloads that may affect the network I/O. 15m
Web Service Statistics – Bytes sent to client com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=web service,facet=bytes sent to client,counterName=* These are useful to track the average request pay load and response pay load for web services and watch for large payloads that may affect the network I/O. 15m
Web Service Statistics – Bytes received from client com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=web service,facet=bytes received from client,counterName=* These are useful to track the average request pay load and response pay load for web services and watch for large payloads that may affect the network I/O. 15m
Web Services Statistics Summary Over Collection Intervals com.ibm.team.foundation.counters:name=<< contextRoot>>, type=webServicesSummary Metrics,facet=*,component=* This bean captures the summary information over collection intervals. The summary includes total count, average over interval, max over interval, transaction rate, the total value over interval etc. The summary bean is create by facet and within each facet you can get a summary by component. 15m
Floating license consumption statistics – Concurrent use com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=Floating license concurrent use,facet=All servers,counterName=* This facet captures the floating license consumption from the servers. 15m
Floating license consumption statistics – Concurrent use com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=Floating license concurrent use,facet=All servers,counterName=* This facet captures the floating license consumption from the servers. 15m
Floating license consumption statistics – License checkout time com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=Floating license checkout time,facet=All servers,counterName=* This facet captures the floating license checkout time from the servers. 15m
Floating license consumption statistics – License Denials com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=Floating license denials,facet=All servers,counterName=* This facet captures the floating license denials from the servers. 15m
Token License consumption statistics – Concurrent use com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group= License token use,facet=All providers,counterName=* This facet captures the token license consumption from the servers. 15m
Token License consumption statistics – License Denials com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group= License token provider denials,facet=All providers,counterName=* This facet captures the token license denials from the providers. 15m
Compatible Client Login Details – Number of logins com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group= Compatible client logins,facet=Number of logins,counterName=* This facet captures the number of login attempts from different versions of the client. This MBean is only available in RTC. 15m
Jazz MQTT Service – Messages Received Count com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=MqttService,facet=Count,counterName=* This facet captures the count of messages received by the Jazz MQTT service. 15m
Jazz MQTT Service – Messages Received Frequency (msgs/sec) com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=MqttService,facet=Frequency (msg/s),counterName=* This facet captures the frequency of messages received by the Jazz MQTT service. 15m
Jazz MQTT Service – Messages Received Reset Counter com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=MqttService,facet=Reset,counterName=* This facet captures the count of reset messages received by the Jazz MQTT service. 15m
Jazz MQTT Service – Messages Sent Count com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=MqttService,facet=Count,counterName=* This facet captures the count of messages sent by the Jazz MQTT service. 15m
Jazz MQTT Service – Messages Sent Frequency (msgs/sec) com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=MqttService,facet=Frequency (msg/s),counterName=* This facet captures the frequency of messages sent by the Jazz MQTT service. 15m
Jazz MQTT Service – Messages Sent Reset Counter com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=MqttService,facet=Reset,counterName=* This facet captures the count of reset messages sent by the Jazz MQTT service. 15m
Jazz MQTT Service – Messages Sent Queued Counter com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=MqttService,facet=Queued,counterName=* This facet captures the count of queued messages to be sent by the Jazz MQTT service. 15m
Jazz MQTT Service – Messages Received Queue Exhausted Counter com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=MqttService,facet=Queue Exhausted,counterName=* This facet captures the count of times when the thread pool size to process received messages has maxed out and the queue to hold excess is full. 15m
Jazz MQTT Service – Published Messages Lost Count com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=MqttService Stats,facet=Send Success rate,counterName=* This facet captures the count of published messages that got lost and did not make it to the broker. 15m
Jazz MQTT Service – Message Processing Time com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=MqttService Stats,facet=Elapsed time in seconds,counterName=* This facet captures the average processing time for handling messages received by the Jazz MQTT service. 15m
Jazz MQTT Service – Message Sent Result - Success com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=MqttService Stats,facet=Send Success rate,counterName=* This facet captures the count of published messages that were successfully delivered to the broker. 15m
Jazz MQTT Service – Message Sent Result - Failure com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=MqttService Stats,facet=Send Success rate,counterName=* This facet captures the count of published messages that failed to be delivered to the broker. 15m
Jazz MQTT Service – Message processed on main thread com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=MqttService Stats,facet=Send Success rate,counterName=* This facet captures the count of received messages that were processed on the main thread in the Jazz MQTT Service as the service was being deactivated and also when the threadpool and the queue to use for holding tasks before they are executed were exhausted. 15m
Jazz MQTT Service – Received Messages - Queue Size com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=MqttService Stats,facet=Arrived Messages Processing,counterName=* This facet captures the size of the queue in MQTT service used to hold incoming messages before a background thread becomes available to process them. 15m
Jazz MQTT Service – Received Messages – thread pool size com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=MqttService Stats,facet=Arrived Messages Processing,counterName=* This facet captures the size of the thread pool used to handle the incoming messages by the Jazz MQTT service. The excess messages will be held in queue. 15m
Jazz MQTT Service – Failed connections to broker com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=MqttService Client Stats,facet=Failed to connect,counterName=* This facet captures the count of failed connections to the broker from the Jazz MQTT service. 15m
Jazz MQTT Service – Lost connections to broker com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=MqttService Client Stats,facet=Connection lost,counterName=* This facet captures the count of lost connections to the broker from the Jazz MQTT service. 15m
Distributed Data Microservice – Key Size com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=Distributed Maps and Values Sizes,facet=Key Size,counterName=* Facet reports the size of the object used as a map Key. 15m
Distributed Data Microservice – Added Value Size com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=Distributed Maps and Values Sizes,facet=Added Value Size,counterName=* This facet reports the size of the data help in the map. 15m
Distributed Data Microservice – Number of Elements in Map com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=Distributed Maps and Values Sizes,facet=Number of Elements in Map,counterName=* This facet reports the number of elements in the map. 15m
Distributed Data Microservice – Bytes transferred (in kb) com.ibm.team.foundation.counters:name=<< contextRoot>>, type=counterMetrics, group=Distributed Persistence Layer,facet=Bytes transferred (in kb) ,counterName=* This facet reports the size of data (in KB) transferred between persistence layer and distributed maps in memory. 15m


Table 4 - Common Bean Attributes


There are six common attributes that MBeans created for jazz based applications share.

Common Attributes Description Type
Domain This is the namespace for the application under which the MBean data is published String
creationTimeStamp This is the time when the MBean was updated with a snapshot of the relevant data Timestamp
host This is the host name where the CLM application is running String
port This is the port number where the CLM application is accessible on the host. The value is -1 if the port is not set. int
contextRoot This is the application root context for the CLM application String
nodeId This is the application node id in case the CLM application is clustered String


Table 5 - Managed Bean Attributes


The specific attributes used by all of the managed beans in the Jazz based applications.

Attributes Description Type
workItemType The type name of the work item type String
scenarioName This is the name of scenario this active service is associated with String
scenarioId This is a unique scenario instance id this active service is associated with String
serviceName This is the name of this active service String
serviceId The id of this active service String
startTime This is the start time of this active service in milliseconds Long
duration This is the total time this active service has been running since it started. This is the current time when the snapshot was taken minus the start time. This is reported in milliseconds Long
serviceMethod This is name of the service method String
userName This is name of the user who initiated this service String
userId This is id of the user who initiated this service String
threadName This is the name of the java thread executing this service String
threadId This is id of the java thread executing this service Long
totalCount This is the total number of active services currently running Long
countExceedingThresholdDuration This is a number of actives services whose execution duration has exceeded the threshold Long
longestDuration This indicates how long has the longest active service been running in milliseconds Long
cpuRatio Count of active services divided by the number of processors on the server Double
thresholdDuration This is duration in milliseconds used for identifying the services who have exceeded the threshold Long
nodeId This is the application node id String
nodeURL This is the URL for the specified node id String
nodeState This is state of the node id. Values are INACTIVE=0, STALE=1 and ACTIVE=2 Integer
intervalDuration This is the collection time interval in seconds Double
unarchivedCount This is the count of the unarchived users in the repository Integer
archivedCount This is the count of the archived users in the repository Integer
totalCount This is the count of the total users in the repository Integer
name This is the name of specific counter String
group This is the group that the counter belongs to String
facet This represents a particular aspect of this counter String
id This represents a unique id for this counter String
value This is the current average value of the scalar counter Long
min This is the minimum value of the scalar counter Long
max This is the maximum value of the scalar counter Long
count This is the current total count of the range counter samples Long
total This is the total value of all the range counter samples Double
min This is the minimum value of the range counter Double
max This is the maximum value of the range counter Double
average This is the average value of the range counter Double
averageOverInterval This is the average value of the range counter for this collection time interval Double
totalOverInterval This is the total value of the range counter for this collection time interval Double
countOverInterval This is the count for this collection time interval Long
intervalDuration This is the collection time interval in seconds Double
transactionRate This is the transaction rate (countover interval/interval duration) in counts per second Double
stdDev This is the standard deviation value of the integral range counter Long
count This is the current total count of the integral range counter samples Long
total This is the total value of all the integral range counter samples Long
min This is the minimum value of the integral range counter Long
max This is the maximum value of the integral range counter Long
average This is the average value of the integral range counter Long
averageOverInterval This is the average value of the integral range counter for this collection time interval Double
totalOverInterval This is the total value of the range counter for this collection time interval Double
countOverInterval This is the count for this collection time interval Long
intervalDuration This is the collection time interval in seconds Double
transactionRate This is the transaction rate (countover interval/interval duration) in counts per second Double
stdDev This is the standard deviation value of the integral range counter Long
poolSize This is the maximum size of the pool Integer
component This represents the component name associated with this web service. Value of UnKnown is returned if component name cannot be derived String
duration This is the time taken in milliseconds to execute the diagnostic for this test id Integer
startTime This is the start time of the diagnostic for this test id Timestamp
statusDesc This is the message describing the status String
detailStatusDesc This is the detailed message describing the outcome of the diagnostic String
status This is the status of the diagnostic. Values are OK, WARN or ERROR String
testId This is id of this specific diagnostic String
nodeId This is the application node id in case the CLM application is clustered. Otherwise value is NA String
Enabled Endpoint is enabled? Boolean
NodeName Name of the appliance String
TimeStamp Date and time Date
Name Name of the endpoint String
TotalConnections Total number of connections Long
ActiveConnections Number of currently active connections Long
BadConnections Number of connections that failed to connect since reset Long
MsgRead Number of messages that are read since reset Long
MsgWrite Number of messages that are written since reset Long
BytesRead Number of bytes read since reset Long
BytesWrite Number of bytes written since reset Long
LostMessageCount Number of messages that are lost since reset Long
WarnMessageCount Warn Message Count Long
ResetTime Time at which the statistics for the topic were reset Date
contributorId This is the id of the user who initiated a request that caused this error String
accessedUrl This is the URL accessed in the system when this error occured String
queryString This is the query string portion of the accessed URL String
activeConfigId This is the active configuration id which the user was working in when the error occured String
errorTime This is the time of error occurence Timestamp
errorId This is the error id String
errorTitle This is the error title String
errorDetails This is the details of the error String
userId This is the user id who initiatied the request that caused this error String
activeConfigName This is the name of the active configuration in which the user was working when this error occured String
errorLevel This is the level of the error. Values are ERROR or WARN String
indexName This is the name of the full text index for the application String
indexLocation This is the location of the full text index on disk String
indexSize This is the size of the full text index on disk in bytes Long
indexName This is the name of the jfs index for the application String
indexFormatType This is type of index. Values are RDF or TEXT String
indexAvailability This reflects the current state of the index. The values are AVAILABLE, SUSPENDED, SUSPENDING, RESUMING, ABORTED, UNCONNECTABLE, RECOVERING or MIGRATION_IN_PROGRESS String
indexSize This is the size on disk of the specific jfs index in bytes Long
indexLastProcessed The timestamp of the last resource indexed by this indexer Date
indexLastReceived The timestamp of the last resource added to the index queue of this indexer Date
indexDataType This is type of data in the index. Values are HISTORY or LIVE String
indexBacklog The number of items waiting to be indexed Integer
indexRemainingTime An estimate of remaining time to finish to processing the indexing operation in milliseconds Long
itemTypeName This is the name of the item type String
dbId This is a unique id assigned to the type in the database Integer
noOfStates This is total number of states that exists in the REPOSITORY.ITEM_STATES system table for this item type Integer
statesSize This is total size of all the states that exists in the REPOSITORY.ITEM_STATES system table for this item type in bytes Long
noOfContents This is total number of content blobs that exists in the REPOSITORY.CONTENT_STORAGE system table for this item type Integer
contentsSize This is total size of content blobs that exists in the REPOSITORY.CONTENT_STORAGE system table for this item type in bytes Long
sizePercentage This is percentage of the total size of this item type in relation to the total size of all item types together Integer
totalSize This is sum of all the content objects and state objects for this item type in bytes Long
totalAllSize This is sum of all the content objects and state objects for all item types in bytes Long
NodeName Name of the appliance String
TimeStamp Date and time Date
MemoryTotalBytes The total amount of physical memory on IBM MessageSight Long
MemoryFreeBytes The amount of physical memory that is available Long
MemoryFreePercent The amount of free memory as a percentage of total physical memory on MQTT Broker Long
ServerVirtualMemoryBytes The amount of virtual memory that is being used by IBM MessageSight Long
ServerResidentSetBytes The amount of physical memory that is being used by IBM MessageSight Long
MessagePayloads The amount of memory that is being consumed by IBM MessageSight for message payloads Long
PublishSubscribe The amount of memory that is being consumed by IBM MessageSight for publish/subscribe data structures Long
Destinations The amount of memory that is being consumed by IBM MessageSight for destinations on which messages can be buffered Long
CurrentActivity The amount of memory that is being consumed by IBM MessageSight for current activity Long
ClientStates The amount of memory that is being consumed by IBM MessageSight for Client States Long
memoryUsedPercent This statistic shows the amount of used memory as a percentage of total physical memory. Integer
intervalDuration This is the collection time interval in seconds Integer
subscriptionName The name of the subscription String
clusterName The name of the cluster in which the application is running. String
bufferedPercent The percentage of the maximum buffered messages that the current buffered messages represent. Double
bufferedMessages The number of published messages that are waiting to be sent to clients. Long
rejectedMessages The number of messages that are rejected because the maximum number of buffered messages was reached when the messages were published to the subscription. Long
discardedMessages The number of messages that are not delivered because they were discarded when the buffer became full. Long
intervalDuration This is the collection time interval in seconds. Integer
duration This is the time taken in milliseconds to execute the data validation for this component Long
startTime This is the start time of the data validation for this component Timestamp
componentId This is id of the component which has registered the data validator String
statusCode The component specific status code describing the outcome of the validation Integer
severity This is severity of the result. Values are OK=0, INFO=1, WARNING=2, ERROR=4 and CANCEL=8 Integer
message This is message describing the outcome of the validation String
exception Returns the low level exception message if there was an error. Otherwise value is NA String
isArchived This is the boolean to indicate is the project area is archived or not Boolean
noOfContributors This is the total contributors associated with this project area Integer
noOfTeams This is total number of team areas within this project area Integer
developmentLines This is the total number of development time liens within this project area Integer
projectName This is name of the project area String
projectId This is id of the project area String
workitemCount This is the total number of work items within this project area Integer
attachmentCount This is total number of attachments within this project area Integer
attachmentTotalLength This is the total size of all the attachments (in bytes) within this project area Long
pleEnablementState This is the PLE enablement state for the project area. Values are OPT_OUT, OPT_IN_SINGLE_STREAM_PER_COMPONENT or OPT_IN_FULL String
totalNoOfComponents This is the total number of components within this project area Long
totalNoOfStreams This is total number of streams for all the components in this project area Long
totalNoOfBaselines This is total number of baselines for all the components in this project area Long
totalNoOfVersionMappings This is total number for version mappings for all concepts in all the project area components Long
MaximumDepthOfRootStream This is maximum depth of any of the root component streams in this project area Long
archivedCount This is total number of archived project areas in this application Integer
unarchivedCount This is the total number of unarchived project areas in this application Integer
totalCount This is total number of project areas in the application Integer
scenarioName This is the name of resource intensize scenario String
scenarioId This is a unique id assigned to this instance of the scenario String
startTime This is the start time of the scenario instance Timestamp
endTime This is end time of the scenario instance Timestamp
userName This is name of the user who initiated the scenario String
isActive This is a boolean value indicating if the scenario is completed or not. If it is not completed then the end time attribute is set as -1 Boolean
duration This is the total time this scenario was running in millisecs. If the scenario is still active then this value is indicating how long it has been running since it started until the current time when the snapshot was taken. If it is not active then it is the end time minus the start time Long
dbPingTime This is the round trip time from the JTS or application server to the database in milliseconds Integer
noOfServicesWithErrorStatus This is a number of services from all components that have failed to initialize Integer
servicesWithErrorStatusMsg This is the error message associated with all the services not fully initialized String
dbConnectionStatus This is the status of the databse connection. Values are ERROR, OK or WARNING. String
dbConnectionStatusMsg This is message associated with an error for the database connection status String
serverstateId The etag of the jpi prefix mappings reflects the complete state of all prefix mappings. If there are no mappings this value is NA String
serverStateMsg This is message associated with when the server state Id indicates that a server renmae has occured String
buildId This is the build id associated with the server String
freeMemory The amount of free memory in the Java Virtual Machine in bytes Long
totalMemory The total amount of memory in the Java virtual machine in bytes Long
maxMemory The maximum amount of memory that the Java virtual machine will attempt to use in bytes Long
sqlHash This is unique hashcode for this specific SQL statement String
sqlStmt This is the SQL statement String
sqlMinTime The smallest execution time (in ms) for all instances of this statement Integer
sqlMaxTime The largest execution time (in ms) for all instances of this statement Integer
sqlTotalTime The total sum execution time (in ms) for all instances of this statement Integer
sqlTotalCount The number of times this statement was executed Integer
sqlAverageTime The average execution time (in ms) for all instances of this statement Float
sqlLastExecutedTimestamp The time this statement was last executed Date
sqlStmtType The type of transaction. Values are read, write or other String
sqlActivityInterval The interval in milliseconds used for capturing the sql activity in this bean Long
sqlTotalTime The total sum execution time (in ms) for all sql statements of this type Integer
sqlTotalCount The number of times this type of statement was executed Integer
sqlAverageTime The average execution time (in ms) for all sql statements of this type Double
sqlStmtTime The type of statement. Values are read, write or other String
sqlActivityInterval The interval in milliseconds used for capturing the sql activity in this bean Long
NodeName Name of the appliance String
TimeStamp Date and time Date
DiskUsedPercent Specifies the percentage of disk space that is used Long
DiskFreeBytes Specifies the amount of disk space that is available Long
MemoryUsedPercent Specifies the percentage of persistent memory that is used, and therefore not available Long
MemoryTotalBytes Total memory in bytes Long
*TotalBytes Pool total bytes Long
*UsedBytes Total used bytes by Pool Long
*UsedPercent Memory in Percent used by Pool Long
*RecordsLimitBytes Pool Records limit in bytes Long
*RecordsUsedBytes Pool Records used memory in bytes Long
NodeName Name of the appliance String
TimeStamp Date and time Date
TopicString The topic that is being monitored. The topic string always contains a wildcard. String
Subscriptions The number of active subscriptions on the topics that are monitored. The figure shows all active subscriptions that match the wildcarded topic string. Long
ResetTime The time at which the statistics for the topic were reset. The ResetTime is usually the time when the topic monitor is created. Date
PublishedMsgs The number of messages that are successfully published to a topic that matches the wildcarded topic string. Long
RejectedMsgs The number of messages that are rejected by one or more subscriptions where the quality of service level did not cause the publish request to fail. Long
FailedPublishes The number of publish requests that failed because the message is rejected by one or more subscriptions. Long
group This is the group that this counter summary belongs to String
facet This represents a particular aspect of this summary String
component This represents the component name associated with this web service summary. Value of UnKnown is returned if component name cannot be derived String
averageOverInterval This is the average value across all range counters for this collection time interval Double
maxOverInterval This is the maximum average value across all range counters for this collection time interval Double
totalOverInterval This is the total value across all range counters for this collection time interval Double
countOverInterval This is the total count across all range counters for this collection time interval Double
intervalDuration This is the collection time interval in seconds Double
transactionRate This is the transaction rate (countover interval/interval duration) in counts per second Double
projectName This is name of the project area String
projectId This is id of the project area String
count This is the total number of work items of this type within this project area Integer



Related topics: Deployment web home, Deployment web home

External links:

Additional contributors: TWikiUser, TWikiUser

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r15 | r7 < r6 < r5 < r4 | More topic actions...
 
This site is powered by the TWiki collaboration platformCopyright © by IBM and non-IBM 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.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.