Chat now with support
Chat with Support

Foglight for DB2 (Cartridge) 5.7.5.50 - User Guide

Introduction to Foglight for DB2 LUW Using Foglight for DB2 LUW Reference
Dashboards and Views Collections and Metrics
CF Locks Collection CF Memory Pools Collection CF Resource Usage Collection Current Agents Details Collection Agents Summary Collection Current Locks Wait Collection Database Bufferpools Summary PS Collection Database Configuration Collection Database Tablespaces Collection Database Tablespaces Summary Collection Database Usability Collection Database Parameters Collection Database Instance Parameters Collection Database Instance Registry Variables Collection Database Tablespaces BP Collection FCM Activity Collection FS DB Storage Collection FS DB Storage Summary Collection FS Instance Storage Collection FS Storage Collection FS Storage Summary Collection General Activity Collection HADR Activity Collection Host Properties Collection OS General Collection Instance Activity Collection Instance General Collection Instance Nodes Collection Instance Usability Collection IO Activity Collection License Details Collection Log Activity Collection Log File Collection Log Message Collection Messages Count Collection Monitor Switches Collection OS DB2 General Process Collection Partition Tablespaces Summary Collection Partition Usability Collection pureScale Alerts Collection Top SQLs Collection Top SQLs Full Text Collection Top SQLs Text Collection Query Agents Details Collection Database Partition Activity Collection DB2 Partition Subcategories Wait Collection History Locks Wait Collection History Locks Summary Collection Instance Memory Collection Instance Memory Pool Collection Instance Memory Summary Collection Instance Memory Total Collection Database Memory Collection Database Memory Pool Collection Database Memory Pool DB Collection Database Memory Summary Collection Database Memory Total Collection Database Buffer Pools Collection Database Tables Collection Database Partition Backup Collection Database Tables Global Collection Database Applications Collection

Database Bufferpools Summary PS Collection

Tracks how members use group buffer pools (GBP) and local buffer pools (LBP).

 
Metric
Description

INSTANCE_NAME

The name of the monitored instance.

DB_NAME

The name of the monitored database.

MEMBER

The name of the database member from which the data was retrieved.

GBP_EFFICENCY

Percentage of pages read from the GBP after the page found in the LBP was found to be invalid. Indicates the amount of time a read from disk was avoided thanks to the GBP.

GBP_HIT_RATIO

pureScale only — Percentage of times a requested page was found in the GBP out of all times it was requested. If a page is found in the GBP, it saves the database the time to look for it in the LBP.

GBP_INVALID_PAGES

Number of GBP data page read attempts due to an LBP page being present but marked invalid.

GBP_LOGICAL_READS

pureScale only — Number of times a GBP-dependent page was attempted to be read from the GBP because the page was either invalid or not present in the LBP.

GBP_PHYSICAL_READS

Number of times a GBP-dependent page was read into the LBP from disk because it was not found in the GBP.

LBP_HIT_RATIO

Percentage of times a requested page was found in the LBP (either valid or invalid) out of all times it was requested.

LBP_LOGICAL_READS

Number of pages (Data, Index, XDA) that were found in the LBP. Value includes both valid and invalid pages.

LBP_PHYSICAL_READS

Number of pages prefetched from the GBP to the LBP.

TOTAL_HIT_RATIO

Percentage of times a requested page was found in the buffer pool out of all times it was requested. If a page is found in the buffer pool, it saves the database the time to look for it in the physical storage.

TOTAL_LOGICAL_READS

Total logical reads (index, XDA and data) requested from the buffer pool.

TOTAL_PHYSICAL_READS

Total pages (index, XDA and data) read from physical storage into the buffer pool.

Database Configuration Collection

The following table provides a list of the Database Configuration metrics that are collected, and a description for each.

 
Metric
Description

DB_NAME

The name of the monitored database.

HADR_DB_ROLE

Standard means that the database is not a HADR DB. Primary or Standby means that it is.

LOGFILESIZE

A parameter that predefines the size of the diag log. If this is set to 0 (the default), the diag log gets larger with no limit. If a size is specified, after the diag log reaches that size, a new file with a new name is created and used.

Database Tablespaces Collection

The following table provides a list of the Database Tablespaces metrics that are collected, and a description for each.

 
Metric
Description

DB_NAME

The name of the monitored database.

TBSP_NAME

The tablespace name.

DBPARTITIONNUM

The database partition from which the data was retrieved for this row.

TABLESPACE_ID

The tablespace ID.

TABLESPACE_STATE

This interface returns a text identifier based on the definitions in sqlutil.h, and is a combination of the following values, separated by a '+' sign:

BACKUP_IN_PROGRESS

BACKUP_PENDING

DELETE_PENDING

DISABLE_PENDING

DROP_PENDING

LOAD_IN_PROGRESS

LOAD_PENDING

NORMAL

OFFLINE

PSTAT_CREATION

PSTAT_DELETION

QUIESCED_EXCLUSIVE

QUIESCED_SHARE

QUIESCED_UPDATE

REBAL_IN_PROGRESS

REORG_IN_PROGRESS

RESTORE_IN_PROGRESS

RESTORE_PENDING

ROLLFORWARD_IN_PROGRESS

ROLLFORWARD_PENDING

STORDEF_ALLOWED

STORDEF_CHANGED

STORDEF_FINAL_VERSION

STORDEF_PENDING

SUSPEND_WRITE

TABLESPACE_USING_AUTO_STORAGE

Specifies whether the tablespace was created as an automatic storage tablespace. A value of 1 indicates yes; a value of 0 indicates no.

TABLESPACE_AUTO_RESIZE_ENABLED

This element is applicable to DMS tablespaces and non-temporary automatic storage tablespaces only. If this element is set to 1, then automatic resizing is enabled.

TABLESPACE_TYPE

This interface returns a text identifier, based on the definitions in sqlutil.h, which is one of the following values:

DMS

SMS

TABLESPACE_FREE_SIZE_MB

The tablespace free size [MB].

TABLESPACE_TOTAL_SIZE_MB

The tablespace total size [MB].

TABLESPACE_USED_SIZE_MB

The tablespace used size [MB].

TABLESPACE_USABLE_SIZE_MB

The tablespace usable size [MB].

TABLESPACE_UTILIZATION_
PERCENT

The percentage of tablespace used.

TABLESPACE_PAGE_SIZE_KB

The tablespace page size (in KB).

TABLESPACE_TOTAL_PAGES

The total operating system space occupied by a tablespace. For DMS, this is the sum of the container sizes (including overhead). For SMS, this is the sum of all the filespace used for the tables stored in this tablespace (and is collected only if the buffer pool switch is on).

TABLESPACE_USABLE_PAGES

The total number of pages in a tablespace minus the overhead pages.

This element is applicable to DMS tablespaces only. For SMS, this element has the same value as TABLESPACE_TOTAL_PAGES.

TABLESPACE_FREE_PAGES

The total number of pages that are currently free in a tablespace.

This is applicable to DMS tablespaces only.

TABLESPACE_USED_PAGES

The total number of pages in use for a DMS tablespace. For an SMS tablespace, this is equal to TABLESPACE_TOTAL_PAGES.

TABLESPACE_PREFETCH_SIZE

The maximum number of pages the prefetcher gets from the disk at a time.

If automatic prefetch size is enabled, this element reports the value -1.

TABLESPACE_EXTENT_SIZE

The tablespace extent size.

TABLESPACE_NUM_CONTAINERS

The number of containers.

FILES_CLOSED

The total number of closed database files.

The database manager opens files for reading and writing into and out of the buffer pool. The maximum number of database files open by an application at any time is controlled by the maxfilop configuration parameter.

TABLESPACE_CONTENT_TYPE

This interface returns a text identifier, based on the definitions in sqlmon.h, which is one of the following values:

ANY

LARGE

SYSTEMP

USRTEMP

TABLESPACE_REBALANCER_MODE

Specifies whether a forward or reverse rebalance is taking place. The potential values (defined in sqlmon.h) are:

SQLM_TABLESPACE_NO_REBAL — no rebalancing taking place

SQLM_TABLESPACE_FWD_REBAL — forward

SQLM_TABLESPACE_REV_REBAL — reverse

This can be used to indicate whether the current rebalance process is removing space from a tablespace or adding space to a tablespace. This is only applicable to a DMS tablespace.

TABLESPACE_LAST_RESIZE_TIME

This element displays a timestamp that represents the last time the size of the tablespace was successfully increased.

For tablespaces that can be automatically resized, this element represents the last time that space was automatically added to the tablespace when it became full, more space was being requested, and the maximum tablespace size had not been reached. This element is only applicable to tablespaces that are enabled to be automatically resized.

TABLESPACE_LAST_RESIZE_FAILED

This element describes whether the last attempt to automatically increase the size of the tablespace failed. A value of 1 indicates yes, and a value of 0 indicates no.

For an automatic storage tablespace, this element may show that there is no space left on any of the database's storage paths. For a non-automatic storage tablespace, a failure means that one of the containers could not be extended because its filesystem was full. Another reason for failure is that the maximum size of the tablespace has been reached. This element is only applicable to tablespaces that are enabled to be automatically resized.

TBSP_CURRENT_SIZE_MB

The current size of DMS tablespace (MB).

For DMS and automatic storage tablespaces, this element represents the total size of all tablespace containers in bytes. This value is equal to the total pages for the tablespace (TABLESPACE_TOTAL_PAGES) multiplied by the tablespace's page size (TABLESPACE_PAGE_SIZE). This element is not applicable for SMS tablespaces or for temporary automatic storage tablespaces.

On tablespace creation, for an automatic storage tablespace, the current size might not match the initial size. The value of current size will be within page size multiplied by extent size multiplied by the number of storage paths of the initial size on creation (usually greater, but sometimes smaller). It will always be less than or equal to TABLESPACE_MAX_SIZE (if set). This is because containers can only grow by full extents, and must be grown as a set.

TBSP_MAX_SIZE_MB

The tablespace max size of DMS tablespace (MB). This element shows the maximum size to which the tablespace can automatically resize or increase.

This represents the maximum size in bytes to which a tablespace that can be automatically resized can automatically increase. If this value is equal to the TABLESPACE_CURRENT_SIZE element, then there is no room for the tablespace to grow. If the value of this element is -1, then the maximum size is considered to be “unlimited”, and the tablespace can automatically resize until the file systems are full or the architectural size limit of the tablespace is reached. (This limit is described in the SQL Limits appendix of the SQL Reference). This element is only applicable to tablespaces that are enabled for automatic resizing.

TABLESPACE_DMS_RESIZE_
UTILIZATION

The percentage of tablespace DMS auto-resize yes and auto-storage no used.

Database Tablespaces Summary Collection

The following table provides a list of the Database Tablespaces Summary metrics that are collected, and a description for each.

 
Metric
Description

OVERALL_FIXED_TABLESPACE_
TOTAL_SIZE_MB

The total size [MB] of fixed DMS tablespaces.

OVERALL_FIXED_TABLESPACE_
USED_SIZE_MB

The overall used size [MB] of fixed DMS tablespace.

OVERALL_FIXED_TABLESPACE_
UTILIZATION

The overall utilization (%) of fixed DMS tablespaces.

OVERALL_AUTO_TABLESPACE_
USED_SIZE_MB

The tablespace total size [MB].

OVERALL_AUTO_TABLESPACE_
UTILIZATION

The overall utilization (%) of AUTO DMS and SMS tablespaces spread across different file systems and hosts used by DB2.

AUTO_STORAGE_STATE

Flag returns 0, 1, or 0, 1.

0 means Fixed

1 means Auto

0, 1 means both

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating