Converse agora com nosso suporte
Chat com o suporte

Foglight for DB2 (Cartridge) 5.9.2.1 - 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

HADR Activity Collection

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

 
Metric
Description

DB_NAME

The name of the monitored database.

DBPARTITIONNUM

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

HADR_ROLE

The current HADR role of the database. The data type of this element is integer. The value for this element is one of the following constants:

SQLM_HADR_ROLE_STANDARD (value = 0): The database is not a HADR database.

SQLM_HADR_ROLE_PRIMARY (value = 1): The database is the primary HADR database.

SQLM_HADR_ROLE_STANDBY (value = 2): The database is the standby HADR database.

HADR_STATE

The current HADR state of the database. The data type of this element is integer. This element should be ignored if the HADR role of the database is standard. If the database has a HADR role of primary or standby, the value for this element is one of the following constants:

SQLM_HADR_STATE_DISCONNECTED (value = 0): The database is not connected to its partner database.

SQLM_HADR_STATE_LOC_CATCHUP (value = 1): The database is doing local catch-up.

SQLM_HADR_STATE_REM_CATCH_PEND (value = 2): The database is waiting to connect to its partner to do remote catch-up.

SQLM_HADR_STATE_REM_CATCHUP (value = 3): The database is doing remote catch-up.

SQLM_HADR_STATE_PEER (value = 4): The primary and standby databases are connected and are in peer state.

HADR_SYNCMODE

The current HADR synchronization mode of the database. The data type of this element is integer. This element should be ignored if the HADR role of the database is standard. If the database has a HADR role of primary or standby, the value for this element is one of the following constants:

SQLM_HADR_SYNCMODE_SYNC: Sync mode

SQLM_HADR_SYNCMODE_NEARSYNC: Nearsync mode

SQLM_HADR_SYNCMODE_ASYNC: Async mode

HADR_CONNECT_STATUS

This element should be ignored if the HADR role of the database is standard. If the database has a HADR role of primary or standby, the value for this element is one of the following constants:

SQLM_HADR_CONN_CONNECTED (value = 0): The database is connected to its partner node.

SQLM_HADR_CONN_DISCONNECTED (value = 1): The database is not connected to its partner node.

SQLM_HADR_CONN_CONGESTED (value = 2 ): The database is connected to its partner node, but the connection is congested. A connection is congested when the TCP/IP socket connection between the primary and standby pair is still alive, but one end cannot send to the other end. For example, the receiving end is not receiving from the socket connection, resulting in a full TCP/IP send space. The reasons for network connection congestion include the following:

•
The network is being shared by too many resources or the network is not fast enough for the transaction volume of the primary HADR node.
•
The server on which the standby HADR node resides is not powerful enough to retrieve information from the communication subsystem at the necessary rate.

HADR_CONNECT_TIME

Shows one of the following:

HADR connection time

HADR congestion time

HADR disconnection time

This element should be ignored if the HADR role of the database is standard. If the database HADR role is primary or standby, the meaning of this element depends on the value of the HADR_CONNECT_STATUS element:

If the value of the HADR_CONNECT_STATUS element is SQLM_HADR_CONN_CONNECTED, then this element shows connection time.

If the value of the HADR_CONNECT_STATUS element is SQLM_HADR_CONN_CONGESTED, then this element shows the time when congestion began.

If the value of the HADR_CONNECT_STATUS element is SQLM_HADR_CONN_DISCONNECTED, then this element shows disconnection time.

If there has been no connection since the HADR engine dispatchable unit (EDU) started, connection status is reported as Disconnected and HADR EDU startup time is used for the disconnection time. Since HADR connect and disconnect events are relatively infrequent, the time is collected and reported even if the DFT_MON_TIMESTAMP switch is off.

HADR_HEARTBEAT

The number of missed heartbeats on the HADR connection. If the HADR role of the database is primary or standby, this element indicates the health of the HADR connection. A heartbeat is a message sent from the other HADR database at regular intervals. If the value for this element is zero, no heartbeats have been missed and the connection is healthy. The higher the value, the worse the condition of the connection.

A HADR database expects at least one heartbeat message from the other database in each quarter of the time interval defined in the HADR_TIMEOUT database configuration parameter or in 30 seconds, whichever is shorter. For example, if the HADR_TIMEOUT value is 80 (seconds), then the HADR database expects at least one heartbeat message from the other database every 20 seconds.

NOTE: The data type of this element is integer.
NOTE: This element should be ignored if the HADR role of the database is standard.

 

Use this element to determine the health of the HADR connection. Use the HADR_ROLE monitor element to determine the HADR role of the database.

HADR_LOCAL_HOST

The local HADR host name. The value is displayed as a host name string or an IP address string such as 1.2.3.4. This element should be ignored if the HADR role of the database is standard.

HADR_LOCAL_SERVICE

The local HADR TCP service. This value is displayed as a service name string or a port number string. This element should be ignored if the HADR role of the database is standard.

HADR_REMOTE_HOST

The remote HADR host name. The value is displayed as a host name string or an IP address string such as 1.2.3.4. This element should be ignored if the HADR role of the database is standard.

HADR_REMOTE_SERVICE

The remote HADR TCP service. This value is displayed as a service name string or a port number string. This element should be ignored if the HADR role of the database is standard.

HADR_REMOTE_INSTANCE

The remote HADR instance name. This element should be ignored if the HADR role of the database is standard.

HADR_TIMEOUT

The number of seconds it takes for a HADR database server to consider a communication attempt to have failed. For an attempt to fail, a HADR database server must not receive a reply message from its partner within the number of seconds specified in this element. This element should be ignored if the HADR role of the database is standard.

HADR_PRIMARY_LOG_FILE

The name of the current log file on the primary HADR database. This element should be ignored if the HADR role of the database is standard.

HADR_PRIMARY_LOG_PAGE

The page number in the current log file indicating the current log position on the primary HADR database. The page number is relative to the log file. For example, page zero is the start of the file. This element should be ignored if the HADR role of the database is standard.

HADR_PRIMARY_LOG_LSN

The current log position of the primary HADR database. Log sequence number (LSN) is a byte offset in the log stream of the database. This element should be ignored if the HADR role of the database is standard.

HADR_STANDBY_LOG_FILE

The name of the current log file on the standby HADR database. This element should be ignored if the HADR role of the database is standard.

HADR_STANDBY_LOG_PAGE

The page number in the current log file indicating the current log position on the standby HADR database. The page number is relative to the log file. For example, page zero is the start of the file. This element should be ignored if the HADR role of the database is standard.

HADR_STANDBY_LOG_LSN

The current log position of the standby HADR database. Log sequence number (LSN) is a byte offset in the log stream of the database. This element should be ignored if the HADR role of the database is standard.

HADR_LOG_GAP_KB

The size (in KB) of the gap between the primary LSN and the standby LSN.

When a log file is truncated, the LSN in the next log file starts as if log file truncation took place, as a result of that creating an LSN hole that contains no log data. Such holes can lead to a situation where the log gap does not reflect the actual log difference between the primary and standby LSN.

HADR_LOG_GAP_KB_RATE

The running log gap rate (in KB/s) between the primary and the standby database.

Host Properties Collection

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

 
Metric
Description
•
DATABASE

The name of the monitored database.

•
PARTITION#

The partition number.

•
PHYSICAL_HOST_NAME

The physical name of the host.

•
MACHINE_MODEL

The machine model.

Example: Sun Fire V240

•
OPERATING_SYSTEM

The operating system.

Example for OS and OS version collections: 64-bit sparcv9 sun4u

•
OPERATING_SYSTEM_VERSION

The version of the operating system.

•
RAM

The amount of machine RAM configured for DB2 servers.

•
NUMBER_OF_CPU

The total number of CPU units available for DB2 servers.

•
NUMBER_OF_IO_DEVICES

The number of IO devices configured on the host.

•
NUMBER_OF_NETWORK_INTERFACES

The number of network interfaces installed on the host.

OS General Collection

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

 
Metric
Description

DATABASE

The name of the monitored database.

DISK_UTILIZATION

The percentage of time the busiest device spent serving system-wide I/O requests. This metric serves as a measure for the system I/O load.

FREE_RAM

The amount of RAM that is free and not used by any of the running processes on the DB2 host.

PARTITION#

The partition number.

RESIDENT_SET_SIZE

The host OS resident memory set size.

SYSTEM_CPU_UTILIZATION

The total CPU consumption by all system processes (including DB2 processes) on the host.

SYSTEM_KERNAL_CPU_UTILIZATION

The percentage of CPU time consumed by the operating system's kernel mode activities (processes).

SYSTEM_USER_CPU_UTILIZATION

The percentage of CPU time consumed by the operating system's user mode activities (processes).

USED_RAM

The total amount of memory (both resident and swapped RAM) consumed by all the operating system’s processes, including DB2 (measured in MB).

USED_RAM_PCT

The percentage of RAM that is used by all the operating system’s processes.

VIRTUAL_SET_SIZE

The host OS virtual memory set size.

Instance Activity Collection

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

 
Metric
Description

AGENTS_CREATED_EMPTY_POOL

The number of agents created due to an empty agent pool, including the number of agents started at DB2 start-up (num_initagents).

AGENTS_REGISTERED

The number of agents registered in the currently monitored database manager instance (coordinator agents and subagents).

AGENTS_STOLEN

Represents the number of idle agents associated with an application that get reassigned to work on a different application.

CON_LOCAL_DBASES

The number of local databases that have applications connected.

DB2_STATUS

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

ACTIVE

QUIESCE_PEND

QUIESCED

DB2START_TIME

The date and time that the database manager was started using the db2start command.

DBPARTITIONNUM

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

INSTANCE_NAME

The name of the monitored instance.

LAST_RESET

The date and time that the monitor counters were reset.

LOCAL_CONNECTIONS

The number of local applications that are currently connected to a database within the database manager instance being monitored.

LOCAL_CONN_EXEC

The number of local applications that are currently connected to a database within the database manager instance being monitored and are currently processing a unit of work.

NUM_NODES_IN_DB2_INSTANCE

The number of partitions on the instance.

PERCENT_OF_AGENTS_IN_USE

Of the maximum agents, the percentage of those agents in use.

PIPED_SORTS_ACCEPTED

The number of piped sorts that have been accepted.

Each active sort on the system allocates memory, which may result in sorting taking up too much of the available system memory.

When the number of accepted piped sorts is low compared to the number requested, you can improve sort performance by adjusting one or both of the following configuration parameters:

sortheap, sheapthres

PIPED_SORTS_REQUESTED

The number of piped sorts that have been requested.

POST_THRESHOLD_SORTS

The number of sorts that have requested heaps after the sort heap threshold has been exceeded.

If this element's value is high, you can increase the sort heap threshold (sheapthres) or adjust applications to use fewer or smaller sorts through SQL query changes.

PRODUCT_NAME

The details of the version of the DB2 instance that is running.

REMOTE_CONN_EXEC

The number of remote applications that are currently connected to a database within the database manager instance being monitored and are currently processing a unit of work.

REMOTE_CONNECTIONS

The current number of connections initiated from remote clients to the instance of the database manager that is being monitored.

SERVICE_LEVEL

The current corrective service level of the DB2 instance.

SORT_HEAP_ALLOCATED

The total number of allocated pages of sort heap space for all sorts.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação