EditAttachPrintable
r2 - 2020-07-21 - 20:57:05 - TimFeeneyYou are here: TWiki >  Deployment Web > DeploymentMonitoring > JMXMBeans > MBeansUsage > CollectingDataMetrics

Collecting data related metrics using JMX MBeans todo.png

Authors: TimFeeney
Build basis: 6.0.6.1 and later

One element of sizing the servers for the IBM ELM solution is the current and projected data scale (along with data shape, user scale and workload). There are also recommended artifact limits to stay within to keep an application performing well. There are a few different MBeans that will help keep track of data counts.

Item Count Details MBean

This bean will list several objects of various types (i.e. different typeName values), such as com.ibm.team.workitem.Attachment when collected for the Engineering Workflow Management (EWM) application. Each object collected has several attributes with those of prime interest being:

  • itemTypeName - the name of the type of item being counted, e.g. com.ibm.team.workitem.Attachment, com.ibm.team.workitem.WorkItem, com.ibm.team.vvc.ChangeSet
  • noOfContents - how many items of this type exist in the application's repository
  • totalSize - the total size in the application's repository for items of this type
  • sizePercentage - the size of this item type as a percentage of all the other item types in the application's repository

A common use of this information is to see what is contributing to the size of a repository database. For the EWM application, workitem attachments often take up a lot of the space. This bean will help track growth of those items typically taking up most space in the repository. Strategies then can be put in place to reduce their size, such as use of the attachment migration utility to remove orphaned attachments.

Further, tracking the number of artifacts in a repository for some applications is important given some applications of known size limits. For example, the Engineering Test Management (ETM) application has been tested with up to 15 million artifacts in v7.0.1. Tracking all the relevant item types that contribute to the overall ETM artifact count size, would be advisable to ensure you stay within the limit and track your growth towards it. This allows you to be proactive in managing growth and taking appropriate actions, such as deploying another application server.

Project Area Information MBean

Whereas the Item Count Details MBean provides data counts at the application repository level, the Project Area Information provides some details on the project areas of an application. There are several attributes of interest, but for purposes of tracking data counts relevant to sizing, consider the following (see the reference documentation for the full list).

  • workitemCount - total number of workitems in an EWM project area
  • attachmentCount - total number of workitem attachments in an EWM project area
  • attachmentTotalLength - total size of workitem attachments in an EWM project area
  • totalNoOfComponents - total number of components in a configuration management enabled project area
  • totalNoOfStreams - total number of streams in a configuration management enabled project area
  • totalNoOfBaselines - total number of baselines in a configuration management enabled project area
  • rmArtifactCount - total number of artifacts in a configuration management enabled DOORS Next project area

various RM MBeans

External links:

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r3 < r2 < r1 | More topic actions...
 
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.