Examining metrics for storage

Edit online

The IBM Health Center tool collects continuous metrics from your AS4 Microservice implementation. This tool is helpful for troubleshooting and for improving performance.

About this task

The IBM Health Center provides metrics about the operation of your AS4 Microservice implementation. These metrics are compiled by using markers that are called MBeans that are then collected to create reports when you request them.

Procedure

Deploy the IBM Health Center tool that is provided with the IBM JDK. Enable the tool on each member in the cluster through JVM start arguments to identify performance inhibitors and resolve them.

On the Java Monitoring and Management Console, select the IBM MEG Storage Bucket Variant that you want to examine. Open the menu to locate Attributes. The values that are associated with the attributes are displayed in another panel.

Note: The manual reset operation that is measured by the SinceReset counts does not affect the starting times of the LastDay, LastHour, and LastMinute measurements. The reset could be used for ad hoc experiments, or, if it were never reset, it could be used for measuring operations since a reboot of AS4 Microservice.

The following attributes are available for inspection:

Table 1. MBean attributes for storage variant
Attribute	Description
`Configuration`	The value of the configuration reported.
`CountDeletes`	The number of DELETE operations, which are listed by the following categories: `attemptedLastDay` - total number of attempts in the previous 24 hours `attemptedLastHour` - total number of attempts in the previous 60 minutes `attemptedLastMinute` - total number of attempts in the previous 60 seconds `attemptedSinceReset` - total number of attempts since the counter reset `successfulLastDay` - number of successful attempts in the previous 24 hours `successfulLastHour` - number of successful attempts in the previous 60 minutes `successfulLastMinute` - number of successful attempts in the previous 60 seconds `successfulSinceReset` - number of successful attempts since the counter reset `failedLastDay` - number of failed attempts in the previous 24 hours `failedLastHour` - number of failed attempts in the previous 60 minutes `failedLastMinute` - number of failed attempts in the previous 60 seconds `failedSinceReset` - number of failed attempts since the counter reset
`CountGets`	The number of GET operations, which are listed by the following categories: `attemptedLastDay` - total number of attempts in the previous 24 hours `attemptedLastHour` - total number of attempts in the previous 60 minutes `attemptedLastMinute` - total number of attempts in the previous 60 seconds `attemptedSinceReset` - total number of attempts since the counter reset `successfulLastDay` - number of successful attempts in the previous 24 hours `successfulLastHour` - number of successful attempts in the previous 60 minutes `successfulLastMinute` - number of successful attempts in the previous 60 seconds `successfulSinceReset` - number of successful attempts since the counter reset `failedLastDay` - number of failed attempts in the previous 24 hours `failedLastHour` - number of failed attempts in the previous 60 minutes `failedLastMinute` - number of failed attempts in the previous 60 seconds `failedSinceReset` - number of failed attempts since the counter reset
`CountPuts`	The number of PUT and POST operations, which are listed by the following categories: `attemptedLastDay` - total number of attempts in the previous 24 hours `attemptedLastHour` - total number of attempts in the previous 60 minutes `attemptedLastMinute` - total number of attempts in the previous 60 seconds `attemptedSinceReset` - total number of attempts since the counter reset `successfulLastDay` - number of successful attempts in the previous 24 hours `successfulLastHour` - number of successful attempts in the previous 60 minutes `successfulLastMinute` - number of successful attempts in the previous 60 seconds `successfulSinceReset` - number of successful attempts since the counter reset `failedLastDay` - number of failed attempts in the previous 24 hours `failedLastHour` - number of failed attempts in the previous 60 minutes `failedLastMinute` - number of failed attempts in the previous 60 seconds `failedSinceReset` - number of failed attempts since the counter reset
`IsRetired`	Whether the variant is retired. The following values are valid: true false
`UptimeInSeconds`	The number of seconds the variant is functioning.
`getUsableSpace`	The remaining usable space available for storage at the level of the bucket variant being examined.
`ByteTransferCounts getBytesPut`	The byte transfer counts for PUT operations, which are listed by the following categories: `getBytesTransferredLastDay` - total bytes transferred in the previous 24 hours `getBytesTransferredLastHour` - total bytes transferred in the previous 60 minutes `getBytesTransferredLastMinute` - total bytes transferred in the previous 60 seconds `getBytesTransferredSinceReset` - total bytes transferred since the counter reset
`ByteTransferCounts getBytesGot`	The byte transfer counts for GET operations, which are listed by the following categories: `getBytesTransferredLastDay` - total bytes transferred in the previous 24 hours `getBytesTransferredLastHour` - total bytes transferred in the previous 60 minutes `getBytesTransferredLastMinute` - total bytes transferred in the previous 60 seconds `getBytesTransferredSinceReset` - total bytes transferred since the counter reset

Select the Storage Reaper that you want to examine. Open the menu to locate Attributes. The values that are associated with the attributes are displayed in another panel.

The following attributes are available for inspection:

Table 2. MBean attributes for storage reaper
Attribute	Description
`Configuration`	The value of the configuration reported.
`ExpirationDateLastReapSession`	The date that is associated with the most recent reap session that occurred.
`ReapCountLastDay`	The number of blobs that are removed by the reaper during the 24 hours before the report.
`ReapCountLastHour`	The number of blobs that are removed by the reaper during the 60 minutes before the report.
`ReapCountLastReapSession`	The number of blobs that are removed by the reaper during the previous session.
`ReapCountLastWeek`	The number of blobs that are removed by the reaper in the previous seven days before the report.
`Status`	The status of the reaper. The following values are valid: `SESSION_ACTIVE` - actively running `REAPING` - actively removing blobs according to settings `WAITING_FOR_NEXT_SESSION` - in between sessions according to `storage.reaper.delay_time_in_minutes` `WAITING_FOR_MEMENTO_ACCUMULATION` - when the number of elapsed days is fewer than `reaper.memento_day_count` `IO_ERROR` - an error during input or output `CONFIG_ERROR` - an error in the configuration settings `ERROR` - an unspecified error `STOPPING` - the reaper is stopping