Foglight for DB2 (Cartridge) 5.7.5.50


Metric	Description
INSTANCE_NAME	The name of the monitored instance.
IS_PARTITIONABLE	Indicates whether the instance is partitioned. Values: 1 — Partitioned 0 — Not partitioned Note: An instance with one partition is considered not partitioned.
IS_PURESCALE	Indicates whether the instance is pureScale. Values: 1 — pureScale 0 — Not pureScale
CONFIGURATION	Indicates the configuration of the instance. Values: Partitioned Non-Partitioned Cluster (for pureScale)
NUM_NODES	The number of members in the instance (partitions in a DPF, and members in a pureScale environment).

Instance Nodes Collection

The following table provides a list of the Instance Nodes (partitions or members) metrics that are collected, and a description for each.


Metric	Description
INSTANCE_NAME	The name of the monitored instance.
NODE_ID	The ID of the partition or member.
HOST_NAME	The machine that was associated with the member when it was first added to the instance.
CURRENT_HOST_NAME	The host on which the node is running. In a pureScale environment, this could be a different host than the one originally configured.
MEMBER_TYPE	Indicates the member type. Values: MEMBER CF
DB_PARTITION_NUM	The partition number. For a pureScale instance, this is always 0.
STATE	The state of the member or cluster. The states for a member are: STARTED STOPPED RESTARTING, WAITING_FOR_FAILBACK ERROR UNKNOWN The states for a cluster caching facility are: STOPPED RESTARTING BECOMING_PRIMARY PRIMARY CATCHUP1 PEER ERROR UNKNOWN.
ALERT	Provides information about alerts on the instance. Values: YES — There is at least one alert. NO — There are no alerts. NULL — Inapplicable

Instance Usability Collection

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


Metric	Description
INSTANCE	The monitored instance.
INSTANCE_AVAILABILITY	The percentage of instance partitions available for the currently running query.

IO Activity Collection

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


Metric	Description
ASYNC_PAGES_READ_PER_REQUEST	The average number of pages in each asynchronous read request.
ASYNC_READ	The total number of asynchronous reads (pages) during the specified time range.
ASYNC_READ_RATE	The number of asynchronous reads (pages) per second during the specified time range.
ASYNC_READ_REQUESTS	The total number of asynchronous read requests during the specified time range.
ASYNC_WRITES	The total number of asynchronous writes (pages) during the specified time range.
ASYNC_WRITES_RATE	The number of asynchronous writes (pages) per second during the specified time range.
BALANCE_AVERAGE_LOGICAL_READ	The balance of logical reads across the partitions. This metric shows how balanced the DB2 is, across its partitions, in terms of the logical reads operations.
BALANCE_AVERAGE_PHYSICAL_READ	The balance of physical reads across the partitions. This metric shows how balanced the DB2 is, across its partitions, in terms of the physical reads operations.
DATA_HIT_RATIO	The hit ratio of data reads that were satisfied from the buffer pool, without having to perform physical read operations.
DB_NAME	The name of the monitored database.
DBPARTITIONNUM	The database partition from which the data was retrieved for this row.
DIRECT_READ_REQS	The number of requests to perform a direct read of one or more sectors of data. To calculate the average number of sectors read by a direct read, you can use the following formula: DIRECT_READS / DIRECT_READ_REQS
DIRECT_READ_TIME	The elapsed time (in milliseconds) required to perform the direct reads.
DIRECT_READS	The number of read operations that do not use the buffer pool. To calculate the average number of sectors read by a direct read, you can use the following formula: DIRECT_READS / DIRECT_READ_REQS
DIRECT_READS_RATE	The direct reads rate (pages per second).
DIRECT_WRITE_REQS	The number of requests to perform a direct write of one or more sectors of data. To calculate the average number of sectors written by a direct write, you can use the following formula: DIRECT_WRITES / DIRECT_WRITE_REQS
DIRECT_WRITE_TIME	The elapsed time (in milliseconds) required to perform the direct writes.
DIRECT_WRITES	The number of write operations that do not use the buffer pool. To calculate the average number of sectors that written by a direct write, use the following formula: DIRECT_WRITES / DIRECT_WRITE_REQS
DIRECT_WRITES_RATE	The direct writes rate (pages per second).
FILES_CLOSED	The total number of database files closed. The database manager opens files for reading and writing into and out of the buffer pool. The maxfilop configuration parameter controls the maximum number of database files open by an application at any time. If that maximum is about to be reached, a file will be closed before a new one is opened. NOTE: The number of files opened may not equal the number of files closed.
INDEX_HIT_RATIO	The hit ratio of index reads that were satisfied from the buffer pool, without having to perform index physical read operations.
LOG_CLEANS_RATIO	The percentage of LSN gap cleans within the total number of cleans.
LOGICAL_READS	The total number of pages that have been requested from the buffer pool (logical),
LOGICAL_READS_RATE	The number of logical reads (pages) per second during the specified time range.
OVERALL_POOL_HIT_RATIO	The overall hit ratio of logical reads to physical reads. That is, the percentage of database page I/O requests that were satisfied from the buffer cache and, therefore, did not have to perform disk reads. This ratio measures how efficiently DB2 is using the memory allocated to its buffer cache.
PHYSICAL_READS	The number of physical reads (pages). Physical reads are used when a connection requests a page that is not already in the buffer cache. Physical read operations from the disk are necessary when accessing new table or index pages. Nevertheless, these operations should be avoided when possible, as requested pages should reside in the DB2 buffer cache memory.
PHYSICAL_READS_RATE	The number of physical reads (pages) per second during the specified time range.
PHYSICAL_WRITES	The total number of times a buffer pool page was physically written to disk.
PHYSICAL_WRITES_RATE	The number of buffer pool pages physically written to disk per second.
POOL_ASYNC_DATA_READ_REQS	The number of asynchronous read requests made by the prefetcher to the operating system. These are typically large block IOs of multiple pages.
POOL_ASYNC_DATA_READS	The number of data pages read in from the tablespace containers (physical) by asynchronous engine dispatchable units (EDUs) for all types of tablespaces.
POOL_ASYNC_DATA_WRITES	The number of times a buffer pool data page was physically written to disk by either an asynchronous page cleaner or a prefetcher. A prefetcher may have written dirty pages to disk to make space for the pages being prefetched.
POOL_ASYNC_INDEX_READ_REQS	The number of asynchronous read requests for index pages.
POOL_ASYNC_INDEX_READS	The number of index pages read in from the tablespace containers (physical) by asynchronous engine dispatchable units (EDUs) for all types of tablespaces.
POOL_ASYNC_INDEX_WRITES	The number of times a buffer pool index page was physically written to disk by either an asynchronous page cleaner or a prefetcher. A prefetcher may have written dirty pages to disk to make space for the pages being prefetched.
POOL_ASYNC_READ_TIME	The total amount of time spent reading in data and index pages from the tablespace containers (physical) by asynchronous engine dispatchable units (EDUs) for all types of tablespaces. The value is given in milliseconds.
POOL_ASYNC_WRITE_TIME	The total elapsed time spent writing data or index pages from the buffer pool to disk by database manager page cleaners.
POOL_ASYNC_XDA_READ_REQS	The number of asynchronous read requests for XML storage object (XDA) data.
POOL_ASYNC_XDA_READS	The number of XML storage object (XDA) data pages read in from the tablespace containers (physical) by asynchronous engine dispatchable units (EDUs) for all types of tablespaces.
POOL_ASYNC_XDA_WRITES	The number of times a buffer pool data page for an XML storage object (XDA) was physically written to disk by either an asynchronous page cleaner or a prefetcher. A prefetcher may have written dirty pages to disk to make space for the pages being prefetched.
POOL_DATA_L_READS	The number of data pages that have been requested from the buffer pool (logical) for regular and large tablespaces.
POOL_DATA_P_READS	The number of data pages read in from the tablespace containers (physical) for regular and large tablespaces.
POOL_DATA_WRITES	The number of times a buffer pool data page was physically written to disk.
POOL_DRTY_PG_STEAL_CLNS	The number of times a page cleaner was invoked because a synchronous write was needed during the victim buffer replacement for the database.
POOL_DRTY_PG_THRSH_CLNS	The number of times a page cleaner was invoked because a buffer pool had reached the dirty page threshold criterion for the database.
POOL_INDEX_L_READS	The number of index pages that have been requested from the buffer pool (logical) for regular and large tablespaces.
POOL_INDEX_P_READS	The number of index pages read in from the tablespace containers (physical) for regular and large tablespaces.
POOL_INDEX_WRITES	The number of times a buffer pool index page was physically written to disk.
POOL_LSN_GAP_CLNS	The number of times a page cleaner was invoked because the logging space used had reached a predefined criterion for the database. This element can be used to help evaluate whether you have enough space for logging or whether you need more log files or larger log files.
POOL_NO_VICTIM_BUFFER	The number of times an agent did not have a preselected victim buffer available. This element can be used to help evaluate whether you have enough page cleaners for a given buffer pool when using proactive page cleaning.
POOL_READ_TIME	The total amount of time spent reading in data and index pages from the tablespace containers (physical) for all types of tablespaces. The value is given in milliseconds.
POOL_TEMP_DATA_L_READS	The number of data pages that have been requested from the buffer pool (logical) for temporary tablespaces.
POOL_TEMP_DATA_P_READS	The number of data pages read in from the tablespace containers (physical) for temporary tablespaces.
POOL_TEMP_INDEX_L_READS	The number of index pages that have been requested from the buffer pool (logical) for temporary tablespaces.
POOL_TEMP_INDEX_P_READS	The number of index pages read in from the tablespace containers (physical) for temporary tablespaces.
POOL_TEMP_XDA_L_READS	The number of pages for XML storage object (XDA) data that have been requested from the buffer pool (logical) for temporary tablespaces.
POOL_TEMP_XDA_P_READS	The number of pages for XML storage object (XDA) data read in from the tablespace containers (physical) for temporary tablespaces.
POOL_WRITE_TIME	The total amount of time spent physically writing data or index pages from the buffer pool to disk. The value is given in milliseconds.
POOL_XDA_L_READS	The number of data pages for XML storage objects (XDAs) that have been requested from the buffer pool (logical) for regular and large tablespaces.
POOL_XDA_P_READS	The number of data pages for XML storage objects (XDAs) read in from the tablespace containers (physical) for regular and large tablespaces.
POOL_XDA_WRITES	The number of times a buffer pool data page for an XML storage object (XDA) was physically written to disk.
PREFETCH_WAIT_TIME	The time an application spent waiting for an I/O server (prefetcher) to finish loading pages into the buffer pool.
SYNC_READS	The total number of synchronous reads (pages) during the specified time range.
SYNC_READS_RATE	The number of synchronous reads (pages) per second during the specified time range.
SYNC_WRITES	The total number of synchronous writes (pages) during the specified time range.
SYNC_WRITES_RATE	The number of synchronous writes (pages) per second during the specified time range.
THRESHOLD_CLEANS_RATIO	The percentage of all page cleans that took place after a buffer pool had reached the criterion defined within the database for dirty page threshold.
UNREAD_PREFETCH_PAGES	The number of pages that the prefetcher read in that were never used. If this number is high, prefetchers are causing unnecessary I/O by reading pages into the buffer pool that are not being used.
VICTIM_CLEANS_RATIO	The percentage of all page cleans that took place because a synchronous write was needed during the victim buffer replacement for the database. A victim page is a clean or dirty page in the buffer pool that is removed because DB2 needs to make room for incoming pages. If a victim page is a dirty page, then the information must be written out to disk.
XML_HIT_RATIO	The hit ratio of XML reads that were satisfied from the buffer pool, without having to perform physical read operations.

Seleziona il prodotto:

Per una maggiore efficacia, compilare l'Obiettivo della chat:

Soluzioni consigliate per il problema

Foglight for DB2 (Cartridge) 5.7.5.50 - User Guide

Instance General Collection

Instance Nodes Collection

Instance Usability Collection

IO Activity Collection