IBM · Overview tab show Postgr eSQL in the Components gr oup: v Click Components to see a single Postgr eSQL gr oup widget that is displayed along with a gr oup widget for every

Monitoring Agent for PostgreSQLVersion 1.0 Fix Pack 15

Reference

IBM

Monitoring Agent for PostgreSQLVersion 1.0 Fix Pack 15

Reference

IBM

NoteBefore using this information and the product it supports, read the information in “Notices” on page 35.

This edition applies to version 1.0.0.15 of the Monitoring Agent for PostgreSQL and to all subsequent releases andmodifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2014, 2018.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Chapter 1. Monitoring Agent forPostgreSQL . . . . . . . . . . . . . 1

Chapter 2. Dashboard . . . . . . . . . 3Default dashboard pages . . . . . . . . . . 3Widgets for the Default dashboard pages . . . . . 3Custom views . . . . . . . . . . . . . . 6

Chapter 3. Thresholds . . . . . . . . 7Predefined thresholds . . . . . . . . . . . 7Customized thresholds . . . . . . . . . . 10

Chapter 4. Attributes . . . . . . . . . 11Data sets for the monitoring agent. . . . . . . 12Attribute descriptions . . . . . . . . . . . 13

Application Availability data set . . . . . . 13Availability data set . . . . . . . . . . 14Connection Num data set. . . . . . . . . 16Database Query Counts data set . . . . . . 17Db Buff Hit Rate data set . . . . . . . . . 18Db CPU data set. . . . . . . . . . . . 19Db Memory data set . . . . . . . . . . 19

Db Num data set . . . . . . . . . . . 19DB Size data set . . . . . . . . . . . . 20Lock Detail data set . . . . . . . . . . 20Locks data set . . . . . . . . . . . . 22Locks Filter data set . . . . . . . . . . 22Locks v96 data set . . . . . . . . . . . 23Performance Object Status data set . . . . . 23Server Info data set . . . . . . . . . . . 26SQL Response Time data set . . . . . . . . 26SQL Statement Perf data set . . . . . . . . 27Take Action Status data set . . . . . . . . 28Thread Pool Status data set . . . . . . . . 29

Accessibility features . . . . . . . . 33

Notices . . . . . . . . . . . . . . 35Trademarks . . . . . . . . . . . . . . 37Terms and conditions for product documentation. . 37IBM Online Privacy Statement . . . . . . . . 38

Index . . . . . . . . . . . . . . . 39

© Copyright IBM Corp. 2014, 2018 iii

iv PostgreSQL Reference

Chapter 1. Monitoring Agent for PostgreSQL

The Monitoring Agent for PostgreSQL offers a central point of management for your PostgreSQLenvironment or application.

The software provides a comprehensive means for gathering the information that is required to detectproblems early and to prevent them. Information is standardized across the system. You can monitormultiple servers from a single console. By using the PostgreSQL you can easily collect and analyzePostgreSQL specific information.

Installing and configuring the agent

Install the monitoring agent on the system where the application that you want to monitor is located.

For more information, see the agent installation and configuration topics in IBM Knowledge Center:v IBM Cloud Application Performance Managementv IBM Cloud Application Performance Management, Private

For supported operating systems, see System Requirements in the APM Developer Center.

© Copyright IBM Corp. 2014, 2018 1

http://www.ibm.com/support/knowledgecenter/SSMKFH

http://www.ibm.com/support/knowledgecenter/SSHLNR

https://developer.ibm.com/apm/docs/system-requirements/

2 PostgreSQL Reference

Chapter 2. Dashboard

Open the Application Performance Dashboard in the Cloud APM console to see a status summary of allyour applications. As you drill down to dashboard pages for specific applications and their supportingelements, more details are available about the selected item.

Use the PostgreSQL dashboard pages to proactively monitor your PostgreSQL deployment. Each pagecontains views with key performance indicators.

When an application that includes PostgreSQL managed resources is selected, the navigator and the StatusOverview tab show PostgreSQL in the Components group:v Click Components to see a single PostgreSQL group widget that is displayed along with a group

widget for every other data source type in the application.v Click the PostgreSQL subgroup to see a group widget for each managed resource in the application.v Click inside a PostgreSQL group widget or click a PostgreSQL managed resource from the navigator

Instances section to open a dashboard page with KPIs from the selected managed resource.

For more information about the KPIs, click

in the view or click

in the dashboard banner.

Default dashboard pagesPostgreSQL

Select the PostgreSQL managed component to drill down to more detailed metrics.

Postgres Detail DashboardSelect a PostgreSQL managed instance to drill down to more detailed metrics.

Additional group widgetsThese pop-up group widgets are displayed after you click a group widget for more details. Somegroup widgets have links to more granular information in a popup widget, described here.

Widgets for the Default dashboard pagesPostgreSQL

Select the PostgreSQL managed component to drill down to more detailed metrics.

The following widgets are available in this dashboard page:

PostgreSQL StatusThis group widget displays the PostgreSQL component summary and provides metrics toindicate the overall health of the PostgreSQL databases.

The following KPIs for the widget are derived from the attributes as described:v Active connections: The total number of active connections, which is the total number

of rows in the pg_stat_activity table. This data is derived from the Connection Numattribute in the KPN CONNECTION NUM data set.

v Current CPU used(%): The total CPU usage percentage, out of the system, of datbaseprocesses ("postgres") since they started. This data is derived from the CPU Valueattribute in the KPN DB CPU data set.

v Disconnected DB: The total number of databases that cannot be connected to or areinactive. This data is derived from the Inactive Db Num attribute in the KPN DB NUMdata set.


v Normal DB: The total number of databases that can be connected to or are active. Thisdata is derived from the Active Db Num attribute in the KPN DB NUM data set.

v Physical memory used(MB): The memory usage of all database processes ("postgres")in MB. This data is derived from the Memory attribute in the KPN DB MEMORY dataset.

v Status: The status of the PostgreSQL server, such as active or inactive. If thePostgreSQL server is inactive, no other KPIs are available until the server is broughtback online.

v Waiting locks: The number of locks on which transactions are waiting. This data isderived from the Lock Sum attribute in the KPN LOCKS FILTER data set.

v Worst buffer hit rate(%): The database buffer hit percentage. This data is derived fromthe Buffer Hit Percentage attribute in the KPN DB BUFF HIT RATE data set.

v Worst SQL execution time(ms): The execution time of the SQL statement inmilliseconds. This data is derived from the Exec Time attribute in the KPN SQLSTATEMENT PERF data set.

Postgres Detail DashboardSelect a PostgreSQL managed instance to drill down to more detailed metrics.


Average Response Time by Operation(ms) - Top 10This group widget displays the top 10 average response times of the SQL statements bydatabase and operation. This widget includes the select, insert, update, and deleteoperations by database.

The following KPIs for the widget are derived from the attributes as described:v DB Name: The database name. This data is derived from the Db Name attribute in the

KPN SQL RESPONSE TIME data set.v Response Time(ms): Is not derived directly from a single attribute. The value is

calculated.

Buffer Hit Rate - Lowest 5Description needed in JSON

The following KPIs for the widget are derived from the attributes as described:v Active Connections: The number of active connections to the respective database. This

data is derived from the Number Active Connections attribute in the KPN DB BUFFHIT RATE data set.

v Allow Connections: Indicates whether the database allows connections. This data isderived from the Db Allow Conn attribute in the KPN DB BUFF HIT RATE data set.

v DB Name: The name of the database. This data is derived from the Database Nameattribute in the KPN DB BUFF HIT RATE data set.

v Hit Rate(%): The database buffer hit percentage.

Database Size - Top 5This group widget displays the top five databases sorted by size in MB and includes allrelated tablespace names.

The following KPIs for the widget are derived from the attributes as described:v DB Name: The name of the database. This data is derived from the Database Name

attribute in the KPN DB SIZE data set.v DB Size(MB): The size of the table space in MB. This data is derived from the Table

Space Size MB attribute in the KPN DB SIZE data set.v Tablespace Used: The name of the table space. This data is derived from the Table

Space Name attribute in the KPN DB SIZE data set.


Request Number by Operation - Top 5 databasesThis group widget displays the top five execution counts of SQL statements by database.This widget includes the select, insert, update, and delete operations by database.


attribute in the KPN DATABASE QUERY COUNTS data set.v Deletes: The number of DELETE SQL statements that ran since the last

pg_stat_statements module was enabled or reset. This data is derived from the DeleteSQL Count attribute in the KPN DATABASE QUERY COUNTS data set.

v Inserts: The number of INSERT SQL statements that ran since the lastpg_stat_statements module was enabled or reset. This data is derived from the InsertSQL Count attribute in the KPN DATABASE QUERY COUNTS data set.

v Selects: The number of SELECT SQL statements that ran since the lastpg_stat_statements module was enabled or reset. This data is derived from the SelectSQL Count attribute in the KPN DATABASE QUERY COUNTS data set.

v Updates: The number of UPDATE SQL statements that ran since the lastpg_stat_statements module was enabled or reset. This data is derived from the UpdateSQL Count attribute in the KPN DATABASE QUERY COUNTS data set.

SQL Statement Execution Time - Slowest 5This group widget displays the five slowest SQL statements according to execution timein milliseconds from all databases.

The following KPIs for the widget are derived from the attributes as described:v Affect Rows: Is not derived directly from a single attribute. The value is calculated.v Avg Time(ms): Is not derived directly from a single attribute. The value is calculated.v DB Name: The database name. This data is derived from the Database Name attribute

in the KPN SQL STATEMENT PERF data set.v SQL Statement: Is not derived directly from a single attribute. The value is calculated.

Waiting Lock Time - Top 5This group widget displays the top five waiting lock times in seconds.


attribute in the KPN LOCK DETAIL data set.v Lock Mode: The lock mode to control concurrent access to data in tables. These modes

can be used for application-controlled locking in situations where MVCC does not givethe desired behavior. This data is derived from the Lock Mode attribute in the KPNLOCK DETAIL data set.

v Waiting Pid: The process id of the transaction process that is waiting for a lock. Thisdata is derived from the Wait PID attribute in the KPN LOCK DETAIL data set.

v Waiting Time(s): Is not derived directly from a single attribute. The value is calculated.

Additional group widgetsThese pop-up group widgets are displayed after you click a group widget for more details. Somegroup widgets have links to more granular information in a popup widget, described here.


Lock DetailThis group widget displays information about the top five waiting lock times. Click anyrow to see a tooltip window that contains lock detail information.

The following KPIs for the widget are derived from the attributes as described:

Chapter 2. Dashboard 5

v DB name: The name of the database. This data is derived from the Database Nameattribute in the KPN LOCK DETAIL data set.

v Holding lock pid: The PID of the transcation process that is holding the lock. This datais derived from the Hold PID attribute in the KPN LOCK DETAIL data set.

v Holding lock sql stmt: The SQL Statement for the transaction that is holding the lock,limited to the first 256 characters of the query. This data is derived from the Hold SQLattribute in the KPN LOCK DETAIL data set.

v ID: The object ID that is waiting for a lock, for example, if the lock type is tuple, it isthe ID of tuple. This data is derived from the Lock Type ID attribute in the KPN LOCKDETAIL data set.

v Lock mode: The lock mode to control concurrent access to data in tables. These modescan be used for application-controlled locking in situations where MVCC does not givethe desired behavior. This data is derived from the Lock Mode attribute in the KPNLOCK DETAIL data set.

v Lock type: The type of the lock object. This data is derived from the Lock Typeattribute in the KPN LOCK DETAIL data set.

v Waiting pid: The process id of the transaction process that is waiting for a lock. Thisdata is derived from the Wait PID attribute in the KPN LOCK DETAIL data set.

v Waiting time(s): The waiting time of the lock in seconds. This data is derived from theWait Time attribute in the KPN LOCK DETAIL data set.

Custom viewsAfter you select an application that includes a PostgreSQL managed resource, the Custom Views tab isavailable for displaying and building custom dashboard pages with attribute values from the PostgreSQL.You can quickly build monitoring pages for an application and save them for viewing.

Only a subset of PostgreSQL attributes, which are the most useful for reporting, are available for customviews. These attributes are shown in italic in Chapter 4, “Attributes,” on page 11.


Chapter 3. Thresholds

Thresholds test for certain conditions on your managed resources, such as memory usage over 95%, andraise an event when the conditions have been met.

The agent comes with predefined thresholds that you can use to monitor your PostgreSQL environment.You can create additional thresholds for the areas of interest.

After you click

System Configuration > Threshold Manager, select PostgreSQL as the data sourcetype to see all the available thresholds.

Predefined thresholdsThe thresholds are organized in the Cloud APM console Threshold Manager by the data set for whichthey were written. The PostgreSQL has the following predefined thresholds:

KPN_Active_Connections_CritThe number of active connections are greater than the critical threshold of 80 or there are noconnections.

The default configuration has the following SQL syntax:

*IF *VALUE KPN_CONNECTION_NUM.Connection_Num *GT 80 *OR *VALUEKPN_CONNECTION_NUM.Connection_Num *EQ 0

This threshold is evaluated every 5 minutes.

The severity of this threshold is Critical.

The threshold is evaluated for each distinct value of the Connection_Num attribute.

This threshold uses the following attributes:Connection_Num.Connection_Num[CONNSUM.CONNNUM].

KPN_Active_Connections_WarnThe number of active connections are greater than the warning threshold of 60.


*IF *VALUE KPN_CONNECTION_NUM.Connection_Num *GT 60 *AND *VALUEKPN_CONNECTION_NUM.Connection_Num *LE 80


The severity of this threshold is Warning.

The threshold is evaluated for each distinct value of the Connection_Num attribute.

This threshold uses the following attributes:Connection_Num.Connection_Num[CONNSUM.CONNNUM].

KPN_Buff_Hit_Percent_CritThe buffer hit rate of PostgreSQL is lower than 75 percent.


*IF *VALUE KPN_DB_BUFF_HIT_RATE.Buffer_Hit_Percentage *LT 75 *AND *VALUEKPN_DB_BUFF_HIT_RATE.Number_Active_Connections *NE 0




The threshold is evaluated for each distinct value of the Database_Name attribute.

This threshold uses the following attributes:Db_Buff_Hit_Rate.Buffer_Hit_Percentage[DBBUFFH.BUFFERHITP],Db_Buff_Hit_Rate.Number_Active_Connections[DBBUFFH.NUMBER_ACT],Db_Buff_Hit_Rate.Database_Name[DBBUFFH.DBNAME].

KPN_Buff_Hit_Percent_WarnThe buffer hit rate of PostgreSQL is lower than 90 percent.


*IF *VALUE KPN_DB_BUFF_HIT_RATE.Buffer_Hit_Percentage *LT 90 *AND *VALUEKPN_DB_BUFF_HIT_RATE.Buffer_Hit_Percentage *GE 75




This threshold uses the following attributes:Db_Buff_Hit_Rate.Buffer_Hit_Percentage[DBBUFFH.BUFFERHITP],Db_Buff_Hit_Rate.Database_Name[DBBUFFH.DBNAME].

KPN_High_CPU_CritThe processor usage is greater than the critical threshold of 80 percent.The processor usage iscalculated by adding the processor usage of all the processes that run on the processor cores. Theprocessor usage can exceed 100% for multi-core processors.


*IF *VALUE KPN_DB_CPU.CPU_Value *GT 80



The threshold is evaluated for each distinct value of the CPU_Value attribute.

This threshold uses the following attributes: Db_CPU.CPU_Value[DBCPU.CPUVALUE].

KPN_High_CPU_WarnThe processor usage is greater than the warning threshold of 50 percent.The processor usage iscalculated by adding the processor usage of all the processes that run on the processor cores. Theprocessor usage can exceed 100% for multi-core processors.


*IF *VALUE KPN_DB_CPU.CPU_Value *GT 50 *AND *VALUE KPN_DB_CPU.CPU_Value *LE 80



The threshold is evaluated for each distinct value of the CPU_Value attribute.

This threshold uses the following attributes: Db_CPU.CPU_Value[DBCPU.CPUVALUE].

KPN_Inactive_DBs_WarnSome databases cannot be accessed because of connection problem or the databases are inactive.


*IF *VALUE KPN_DB_NUM.Inactive_Db_Num *GT 0




The threshold is evaluated for each distinct value of the Inactive_Db_Num attribute.

This threshold uses the following attributes: Db_Num.Inactive_Db_Num[DBNUM.DBNUMIN].

KPN_Physical_Memory_High_CritThe physical memory that the database processes use is greater than the critical threshold of oneGB.


*IF *VALUE KPN_DB_MEMORY.Memory *GT 1024



The threshold is evaluated for each distinct value of the Memory attribute.

This threshold uses the following attributes: Db_Memory.Memory[DBMEM.MEMORY].

KPN_Physical_Memory_High_WarnThe physical memory that the database processes use is greater than the warning threshold of 600MB.


*IF *VALUE KPN_DB_MEMORY.Memory *GT 600 *AND *VALUE KPN_DB_MEMORY.Memory *LE 1024



The threshold is evaluated for each distinct value of the Memory attribute.

This threshold uses the following attributes: Db_Memory.Memory[DBMEM.MEMORY].

KPN_PostgreSQL_Locks_CritThe number of waiting locks in PostgreSQL are greater than the critical threshold.


*IF *VALUE KPN_LOCKS_FILTER.Lock_Sum *GT 5



The threshold is evaluated for each distinct value of the Lock_Sum attribute.

This threshold uses the following attributes: Locks_Filter.Lock_Sum[LOCKSF.LOCKSUM].

KPN_PostgreSQL_Locks_WarnThe number of waiting locks in PostgreSQL are greater than the warning threshold.


*IF *VALUE KPN_LOCKS_FILTER.Lock_Sum *GT 0 *AND *VALUE KPN_LOCKS_FILTER.Lock_Sum *LE 5



The threshold is evaluated for each distinct value of the Lock_Sum attribute.

This threshold uses the following attributes: Locks_Filter.Lock_Sum[LOCKSF.LOCKSUM].

KPN_PostgreSQL_Service_DownThe PostgreSQL service is down.


*IF *VALUE KPN_APPLICATION_AVAILABILITY.Status *EQ ’down’

Chapter 3. Thresholds 9

This threshold is evaluated every 1 minute.


The threshold is evaluated for each distinct value of the Status attribute.

This threshold uses the following attributes: Application_Availability.Status[APPAVL1.APPSTA].

KPN_SQL_Statement_Perf_CritThe execution time of the SQL statement is greater than five seconds.


*IF *VALUE KPN_SQL_STATEMENT_PERF.Exec_Time *GT 5000




This threshold uses the following attributes:SQL_Statement_Perf.Exec_Time[SQLPERF.EXECTIME],SQL_Statement_Perf.Query_Info[SQLPERF.QUERYINFO] (not visible in the UI).

KPN_SQL_Statement_Perf_WarnThe execution time of the SQL statement is greater than one second.


*IF *VALUE KPN_SQL_STATEMENT_PERF.Exec_Time *GT 1000 *AND *VALUEKPN_SQL_STATEMENT_PERF.Exec_Time *LE 5000




This threshold uses the following attributes:SQL_Statement_Perf.Exec_Time[SQLPERF.EXECTIME],SQL_Statement_Perf.Query_Info[SQLPERF.QUERYINFO] (not visible in the UI).

Customized thresholdsYou can use the predefined thresholds as a starting point for event monitoring, and create your ownthresholds as conditions arise that you want to monitor.

The PostgreSQL has many data sets that you can use to create thresholds to monitor for specificconditions. For descriptions of the data sets, see Chapter 4, “Attributes,” on page 11.

Tip: The hover help for the Threshold Editor Data set field has a Learn more link to the attributedescriptions for the selected data set.


Chapter 4. Attributes

Attributes are the application properties that are being measured and reported by the Monitoring Agentfor PostgreSQL. Attributes make up the key performance indicators (KPIs) that are reported, and you canuse them to create thresholds for conditions that you want to monitor.

About attributes

Attributes are organized into data sets (also referred to as attribute groups). The values can be selectivelydisplayed in dashboard pages or used to define a threshold.

The most recent data sample of the attributes in the data set are used after you open a dashboard page orstart a threshold.

Dashboard pagesOnly a subset of PostgreSQL attributes is displayed in the dashboard pages. Queries to thedashboard data provider specify which attribute values to request from the managed resource.These attributes are shown in italic in this chapter. You can use these attributes to create thecharts and tables in custom dashboard pages.

ThresholdsYou can define thresholds that monitor the state of your operating system, database, orapplication and open an event when the threshold is exceeded. You use attributes to definethresholds that describe a condition that you want to test. After the threshold is started, theattribute values that are specified in the threshold are compared with the values collected by thePostgreSQL. After the condition is met, an event is registered and you are alerted by indicators inthe Application Performance Dashboard navigator, All My Applications summary boxes, and theEvents tab.

The PostgreSQL comes with predefined thresholds that are enabled and started with the agent. Ifyou edit a predefined threshold, such as to change the condition or severity, it is no longertreated as a predefined threshold but considered a custom threshold.

All PostgreSQL attributes, unless otherwise noted, can be used to create custom thresholds. TheEvents tab has a table of open events with information, including threshold name, severity,source, and display item. You can expand an event row to see the formula and drill down to thedashboard page for the managed resource.

Some attributes names display differently in the Threshold Editor, as shown in parentheses afterthe name, such as “Object Count (OBJECT_COUNT)”.

Historical data configurationsThe PostgreSQL collects historical data for key data sets that are shown in the dashboard pages.A page that includes historical views from the managed resource instance has a time selector toolfor adjusting the time range. With line charts, you can also compare the values with a previousday, up to the number of days that have been saved.

Additional information about attributes

Note the following conditions:v When no data can be collected for a data set, an empty result is returned (no rows of data)v When a specific attribute cannot be collected, the value 0 or “” is returned unless otherwise specified in

a particular attribute (for example, “N/A”)v Any numeric attribute value that is greater than the largest (positive or negative) number that can be

represented by that type returns the corresponding maximum or minimum value (for example, the


maximum value for a 32-bit number is 2,147,483,647). These values are displayed as text values that aredefined by the data set, such as “Value Exceeds Maximum” or “Value Exceeds Minimum”.

Numeric attributes have characteristics that are indicated in parentheses after the data type, such as“(32-bit numeric property)”. A numeric attribute value can be 32-bit or 64-bit or some other size. Thevalue type can be gauge, which means it varies, like a speedometer; counter, which counts and alwaysincreases; or numeric property, such as disk size.

For a list of the data sets, a list of the attributes in each data set, and descriptions of the attributes in thePostgreSQL, see “Data sets for the monitoring agent” and “Attribute descriptions” on page 13.

Data sets for the monitoring agentThe PostgreSQL contains the following data sets.v Data set name: Application Availability

– Table name: KPNAPPAVL1– Historical table name: KPN_APPLICATION_AVAILABILITY or KPNAPPAVL1

v Data set name: Availability– Table name: KPNAVAIL– Historical table name: KPN_AVAILABILITY or KPNAVAIL

v Data set name: Connection Num– Table name: KPNCONNSUM– Historical table name: KPN_CONNECTION_NUM or KPNCONNSUM

v Data set name: Database Query Counts– Table name: KPNDATABAS– Historical table name: KPN_DATABASE_QUERY_COUNTS or KPNDATABAS

v Data set name: Db Buff Hit Rate– Table name: KPNDBBUFFH– Historical table name: KPN_DB_BUFF_HIT_RATE or KPNDBBUFFH

v Data set name: Db CPU– Table name: KPNDBCPU– Historical table name: KPN_DB_CPU or KPNDBCPU

v Data set name: Db Memory– Table name: KPNDBMEM– Historical table name: KPN_DB_MEMORY or KPNDBMEM

v Data set name: Db Num– Table name: KPNDBNUM– Historical table name: KPN_DB_NUM or KPNDBNUM

v Data set name: DB Size– Table name: KPNDBSIZE– Historical table name: KPN_DB_SIZE or KPNDBSIZE

v Data set name: Lock Detail– Table name: KPNLOCKDET– Historical table name: KPN_LOCK_DETAIL or KPNLOCKDET

v Data set name: Locks– Table name: KPNLOCKS– Historical table name: KPN_LOCKS


v Data set name: Locks Filter– Table name: KPNLOCKSF– Historical table name: KPN_LOCKS_FILTER or KPNLOCKSF

v Data set name: Locks v96– Table name: KPNLOCKSN– Historical table name: KPN_LOCKS_V96 or KPNLOCKSN

v Data set name: Performance Object Status– Table name: KPNPOBJST– Historical table name: KPN_PERFORMANCE_OBJECT_STATUS or KPNPOBJST

v Data set name: Server Info– Table name: KPNSVRINFO– Historical table name: KPN_SERVER_INFO or KPNSVRINFO

v Data set name: SQL Response Time– Table name: KPNSQLRESP– Historical table name: KPN_SQL_RESPONSE_TIME or KPNSQLRESP

v Data set name: SQL Statement Perf– Table name: KPNSQLPERF– Historical table name: KPN_SQL_STATEMENT_PERF or KPNSQLPERF

v Data set name: Take Action Status– Table name: KPNTACTST– Historical table name: KPN_TAKE_ACTION_STATUS or KPNTACTST

v Data set name: Thread Pool Status– Table name: KPNTHPLST– Historical table name: KPN_THREAD_POOL_STATUS or KPNTHPLST

Attribute descriptionsAttributes in each PostgreSQL data set collect data that the agent uses for monitoring.

The descriptions of the data sets contain information such as description, type, and names for eachattribute in the data set. Some attributes are designated as key attributes, which are identifier attributesfor the data set. An attribute in italic indicates that it is available for display in the Cloud APM consoledashboard pages.

Application Availability data setThe Application Availability data set provides information about the availability of the PostgreSQLservice. A data sample is sent to the server every minute and is maintained for 8 days by default.

This data set contains the following attributes:

Node The managed system name of the agent. This attribute is a key attribute. The type is string.

The following names are defined for this attribute: NODE (historical name), Node (caption),ORIGINNODE (attribute name), and ORIGINNODE (column name).

Status The status of the PostgreSQL service, such as up or down. This attribute is a key attribute. Thetype is string.

The following names are defined for this attribute: STATUS or APPSTA (historical name), Status(caption), Status (attribute name), and APPSTA (column name).

Chapter 4. Attributes 13

TimestampThe local time at the agent when the data was collected. The type is string.

The following names are defined for this attribute: TIMESTAMP (historical name), Timestamp(caption), Timestamp (attribute name), and TIMESTAMP (column name).

Availability data setThe Availability data set contains the availability data for all processes and services that make up thisapplication.


Application ComponentThe descriptive name of a part of the application. This attribute is a key attribute. The type isstring.

The following names are defined for this attribute: APPLICATION_COMPONENT orCOMPONENT (historical name), Application Component (caption), Application_Component(attribute name), and COMPONENT (column name).

Command LineThe program name and any arguments specified on the command line when the process wasstarted. For Service or Functionality test, this attribute has the value N/A. The type is string withenumerated values. The following values are defined: N/A (N/A). Any value that does not havea definition here is displayed in the User Interface.

The following names are defined for this attribute: COMMAND_LINE or CMDLINE (historicalname), Command Line (caption), Command_Line (attribute name), and CMDLINE (columnname).

Full NameThe full name of the process that includes the path. The type is string with enumerated values.The following values are defined: N/A (N/A). Any value that does not have a definition here isdisplayed in the User Interface.

The following names are defined for this attribute: FULL_NAME or FULLNAME (historicalname), Full Name (caption), Full_Name (attribute name), and FULLNAME (column name).

Functionality Test MessageThe text message that corresponds to the Functionality Test Status. This attribute is only valid forfunctionality tests. The type is string with enumerated values. The following values are defined:N/A (N/A). Any value that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: FUNCTIONALITY_TEST_MESSAGE orFUNCMSG (historical name), Functionality Test Message (caption), Functionality_Test_Message(attribute name), and FUNCMSG (column name).

Functionality Test StatusThe return code of the functionality test. When the monitored application is running correctly,'SUCCESS' is displayed. 'NOT_RUNNING' is displayed when it is not running correctly. 'N/A' isdisplayed when the row does not represent a functionality test. The type is integer withenumerated values. The following values are defined: SUCCESS (0), N/A (1), GENERAL ERROR(2), WARNING (3), NOT RUNNING (4), DEPENDENT NOT RUNNING (5), ALREADYRUNNING (6), PREREQ NOT RUNNING (7), TIMED OUT (8), DOESNT EXIST (9), UNKNOWN(10), DEPENDENT STILL RUNNING (11), INSUFFICIENT USER AUTHORITY (12). Any valuethat does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: FUNCTIONALITY_TEST_STATUS orFUNCSTATUS (historical name), Functionality Test Status (caption), Functionality_Test_Status(attribute name), and FUNCSTATUS (column name).


Name The name of the process, service, or functionality test. This name matches the executable name ofthe process, the service short name or the name of the process used to test the application. Thetype is string with enumerated values. The following values are defined: N/A (N/A). Any valuethat does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: NAME (historical name), Name (caption),Name (attribute name), and NAME (column name).



Page Faults per SecThe rate of page faults for the process measured in faults per second. This attribute contains onlyvalid data for processes. The type is integer (32-bit gauge).

The following names are defined for this attribute: PAGE_FAULTS_PER_SEC or PAGEFAULTS(historical name), Page Faults per Sec (caption), Page_Faults_per_Sec (attribute name), andPAGEFAULTS (column name).

Percent Privileged TimeThe percentage of the available CPU time being used by this process for privileged operation.The type is integer (32-bit gauge).

The following names are defined for this attribute: PERCENT_PRIVILEGED_TIME or PERCPRIV(historical name), Percent Privileged Time (caption), Percent_Privileged_Time (attribute name),and PERCPRIV (column name).

Percent Processor TimeThe percentage of the elapsed time that this process used the processor to execute instructions.The type is integer (32-bit gauge).

The following names are defined for this attribute: PERCENT_PROCESSOR_TIME or PERCPROC(historical name), Percent Processor Time (caption), Percent_Processor_Time (attribute name), andPERCPROC (column name).

Percent User Mode TimeThe percentage of the available CPU time being used by this process for user mode operation.The type is integer (32-bit gauge).

The following names are defined for this attribute: PERCENT_USER_MODE_TIME or PERCUSER(historical name), Percent User Mode Time (caption), Percent_User_Mode_Time (attribute name),and PERCUSER (column name).

PID The process ID associated with the process. This attribute contains only valid data for processes.The type is integer (32-bit gauge).

The following names are defined for this attribute: PID (historical name), PID (caption), PID(attribute name), and PID (column name).

Status The status of the application component.v For processes 'UP', 'DOWN', 'WARNING', or 'PROCESS_DATA_NOT_AVAILABLE':

'PROCESS_DATA_NOT_AVAILABLE' is displayed for a process when the matching process isrunning but the resource use information cannot be collected for that process.

v For services 'UP', 'DOWN', or 'UNKNOWN': 'UNKNOWN' is displayed when the service is notinstalled.

v For functionality tests: 'PASSED' or 'FAILED' is displayed.

The type is integer with enumerated values. The following values are defined: DOWN (0), UP (1),WARNING (2), UNKNOWN (3), PASSED (4), FAILED (5), PROCESS DATA NOT AVAILABLE (6).Any value that does not have a definition here is displayed in the User Interface.


The following names are defined for this attribute: STATUS (historical name), Status (caption),Status (attribute name), and STATUS (column name).

Thread CountThe number of threads currently allocated by this process. This attribute contains only valid datafor processes. The type is integer (32-bit gauge).

The following names are defined for this attribute: THREAD_COUNT or THREADS (historicalname), Thread Count (caption), Thread_Count (attribute name), and THREADS (column name).



Type The type of the application component. Components are processes, services, or functionality tests.The type is integer with enumerated values. The following values are defined: PROCESS (0),SERVICE (1), FUNCTIONALITY TEST (2). Any value that does not have a definition here isdisplayed in the User Interface.

The following names are defined for this attribute: TYPE (historical name), Type (caption), Type(attribute name), and TYPE (column name).

Virtual SizeThe virtual size (in MB) of the process. The type is integer (32-bit gauge).

The following names are defined for this attribute: VIRTUAL_SIZE or VIRTSIZE (historicalname), Virtual Size (caption), Virtual_Size (attribute name), and VIRTSIZE (column name).

Working Set SizeThe working set size of the process in MB. This attribute contains only valid data for processes.The type is integer (32-bit gauge).

The following names are defined for this attribute: WORKING_SET_SIZE or WORKSET(historical name), Working Set Size (caption), Working_Set_Size (attribute name), and WORKSET(column name).

Connection Num data setThe data set provides the number of active connections. A data sample is sent to the server every 5minutes and is maintained for 8 days by default.


Connection NumThe total number of active connections, which is the total number of rows in the pg_stat_activitytable. This attribute is a key attribute. The type is integer (64-bit gauge).

The following names are defined for this attribute: CONNECTION_NUM or CONNNUM(historical name), Connection Num (caption), Connection_Num (attribute name), and CONNNUM(column name).






Database Query Counts data setThe execution count of SQL statements by the respective databases. A data sample is sent to the serverevery minute and is maintained for 8 days by default.


Database NameThe name of the database. This attribute is a key attribute. The type is string.

The following names are defined for this attribute: DATABASE_NAME or DBNAME (historicalname), Database Name (caption), Database_Name (attribute name), and DBNAME (column name).

Delete SQL CountThe number of DELETE SQL statements that ran since the last pg_stat_statements module wasenabled or reset. The type is integer with enumerated values. The following values are defined:No value (-1). Any value that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: DELETE_SQL_COUNT or DELETE_SQL(historical name), Delete SQL Count (caption), Delete_SQL_Count (attribute name), andDELETE_SQL (column name).

Insert SQL CountThe number of INSERT SQL statements that ran since the last pg_stat_statements module wasenabled or reset. The type is integer with enumerated values. The following values are defined:No value (-1). Any value that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: INSERT_SQL_COUNT or INSERT_SQL(historical name), Insert SQL Count (caption), Insert_SQL_Count (attribute name), andINSERT_SQL (column name).



Select SQL CountThe number of SELECT SQL statements that ran since the last pg_stat_statements module wasenabled or reset. The type is integer with enumerated values. The following values are defined:No value (-1). Any value that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: SELECT_SQL_COUNT or SELECT_SQL(historical name), Select SQL Count (caption), Select_SQL_Count (attribute name), andSELECT_SQL (column name).



Total CountThe number of SQL statements that ran since the last pg_stat_statements module was enabled orreset. The type is integer (64-bit gauge).

The following names are defined for this attribute: TOTAL_COUNT or TOTAL_PER_ (historicalname), Total Count (caption), Total_Count (attribute name), and TOTAL_PER_ (column name).

Update SQL CountThe number of UPDATE SQL statements that ran since the last pg_stat_statements module wasenabled or reset. The type is integer with enumerated values. The following values are defined:No value (-1). Any value that does not have a definition here is displayed in the User Interface.


The following names are defined for this attribute: UPDATE_SQL_COUNT or UPDATE_SQL(historical name), Update SQL Count (caption), Update_SQL_Count (attribute name), andUPDATE_SQL (column name).

Db Buff Hit Rate data setThe buffer hit percentage data set provides information about the hit percentage of all buffers that areavailable for the database. A data sample is sent to the server every 5 minutes and is maintained for 8days by default.


Buffer Hit PercentageThe database buffer hit percentage. The type is real number (32-bit gauge) with two decimalplaces of precision with enumerated values. The following values are defined: No activeconnections (101). Any value that does not have a definition here is displayed in the UserInterface.

The following names are defined for this attribute: BUFFER_HIT_PERCENTAGE or BUFFERHITP(historical name), Buffer Hit Percentage (caption), Buffer_Hit_Percentage (attribute name), andBUFFERHITP (column name).



Db Allow ConnIndicates whether the database allows connections. The type is string with enumerated values.The following values are defined: true (true), false (false). Any value that does not have adefinition here is displayed in the User Interface.

The following names are defined for this attribute: DB_ALLOW_CONN or DBAWCONN(historical name), Db Allow Conn (caption), Db_Allow_Conn (attribute name), and DBAWCONN(column name).



Number Active ConnectionsThe number of active connections to the respective database. The type is integer (32-bit gauge).

The following names are defined for this attribute: NUMBER_ACTIVE_CONNECTIONS orNUMBER_ACT (historical name), Number Active Connections (caption),Number_Active_Connections (attribute name), and NUMBER_ACT (column name).



Buffer Hit PercentThe database buffer hit percentage. 101 represents 'No active connections' The type is real number(32-bit gauge) with two decimal places of precision.

The following names are defined for this attribute: BUFFER_HIT_PERCENT or BUFFER_HIT(historical name), Buffer Hit Percent (caption), Buffer_Hit_Percent (attribute name), andBUFFER_HIT (column name).


Db CPU data setThe total CPU usage percentage, out of the system, of database processes ("postgres") since they started.A data sample is sent to the server every minute and is maintained for 8 days by default.


CPU ValueThe total CPU usage percentage, out of the system, of datbase processes ("postgres") since theystarted. This attribute is a key attribute. The type is real number (32-bit gauge) with one decimalplaces of precision with enumerated values. The following values are defined: N/A (-1). Anyvalue that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: CPU_VALUE or CPUVALUE (historical name),CPU Value (caption), CPU_Value (attribute name), and CPUVALUE (column name).





Db Memory data setThe memory usage of all database processes ("postgres") in MB. A data sample is sent to the server every2 minutes and is maintained for 8 days by default.


MemoryThe memory usage of all database processes ("postgres") in MB. This attribute is a key attribute.The type is real number (32-bit gauge) with one decimal places of precision with enumeratedvalues. The following values are defined: N/A (-1). Any value that does not have a definitionhere is displayed in the User Interface.

The following names are defined for this attribute: MEMORY (historical name), Memory (caption),Memory (attribute name), and MEMORY (column name).





Db Num data setThe total number of databases, both inactive and active. A data sample is sent to the server every 5minutes and is maintained for 8 days by default.


Active Db NumThe total number of databases that can be connected to or are active. This attribute is a keyattribute. The type is integer (32-bit gauge).


The following names are defined for this attribute: ACTIVE_DB_NUM or DBNUMAC (historicalname), Active Db Num (caption), Active_Db_Num (attribute name), and DBNUMAC (columnname).

Inactive Db NumThe total number of databases that cannot be connected to or are inactive. This attribute is a keyattribute. The type is integer (32-bit gauge).

The following names are defined for this attribute: INACTIVE_DB_NUM or DBNUMIN(historical name), Inactive Db Num (caption), Inactive_Db_Num (attribute name), and DBNUMIN(column name).





DB Size data setData size information for respective databases in MB. A data sample is sent to the server every 5 minutesand is maintained for 8 days by default.






Table Space NameThe name of the table space. This attribute is a key attribute. The type is string.

The following names are defined for this attribute: TABLE_SPACE_NAME or TSNAME (historicalname), Table Space Name (caption), Table_Space_Name (attribute name), and TSNAME (columnname).

Table Space Size MBThe size of the table space in MB. The type is integer (32-bit gauge).

The following names are defined for this attribute: TABLE_SPACE_SIZE_MB or TSSIZE (historicalname), Table Space Size MB (caption), Table_Space_Size_MB (attribute name), and TSSIZE (columnname).



Lock Detail data setThe data set provides detailed information about the database locks. A data sample is sent to the serverevery minute and is maintained for 8 days by default.





Hold PIDThe PID of the transcation process that is holding the lock. This attribute is a key attribute. Thetype is integer (32-bit numeric property).

The following names are defined for this attribute: HOLD_PID or HOLDPID (historical name),Hold PID (caption), Hold_PID (attribute name), and HOLDPID (column name).

Hold SQLThe SQL Statement for the transaction that is holding the lock, limited to the first 256 charactersof the query. The type is string.

The following names are defined for this attribute: HOLD_SQL or HOLDSQL (historical name),Hold SQL (caption), Hold_SQL (attribute name), and HOLDSQL (column name).

Lock ModeThe lock mode to control concurrent access to data in tables. These modes can be used forapplication-controlled locking in situations where MVCC does not give the desired behavior. Thetype is string.

The following names are defined for this attribute: LOCK_MODE or LOCKMODE (historicalname), Lock Mode (caption), Lock_Mode (attribute name), and LOCKMODE (column name).

Lock Type IDThe object ID that is waiting for a lock, for example, if the lock type is tuple, it is the ID of tuple.The type is string.

The following names are defined for this attribute: LOCK_TYPE_ID or LOCKTYPEID (historicalname), Lock Type ID (caption), Lock_Type_ID (attribute name), and LOCKTYPEID (column name).

Lock TypeThe type of the lock object. The type is string.

The following names are defined for this attribute: LOCK_TYPE or LOCKTYPE (historical name),Lock Type (caption), Lock_Type (attribute name), and LOCKTYPE (column name).





Wait PIDThe process id of the transaction process that is waiting for a lock. This attribute is a keyattribute. The type is integer (32-bit numeric property).

The following names are defined for this attribute: WAIT_PID or WAITPID (historical name), WaitPID (caption), Wait_PID (attribute name), and WAITPID (column name).

Wait TimeThe waiting time of the lock in seconds. The type is string.

The following names are defined for this attribute: WAIT_TIME or WAITTIME (historical name),Wait Time (caption), Wait_Time (attribute name), and WAITTIME (column name).


Hold App NameThe name of the application that is holding the lock. The type is string.

The following names are defined for this attribute: HOLD_APP_NAME or HOLDAPPNAM(historical name), Hold App Name (caption), Hold_App_Name (attribute name), andHOLDAPPNAM (column name).

Wait App NameThe name of the application that is waiting for the lock. The type is string.

The following names are defined for this attribute: WAIT_APP_NAME or WAITAPPNAM(historical name), Wait App Name (caption), Wait_App_Name (attribute name), andWAITAPPNAM (column name).

Locks data setThe number of locks on which one or more transactions are waiting.


Lock SumThe number of locks on which transactions are waiting. This attribute is a key attribute. The typeis integer (64-bit gauge).

The following names are defined for this attribute: LOCK_SUM or LOCKSUM (historical name),Lock Sum (caption), Lock_Sum (attribute name), and LOCKSUM (column name).





Locks Filter data setThe number of locks on which one or more transactions are waiting. A data sample is sent to the serverevery minute and is maintained for 8 days by default.









Locks v96 data setThe number of locks on which one or more transactions are waiting.








Performance Object Status data setThe Performance Object Status data set contains information that reflects the status of other data sets soyou can see the status of all performance objects that make up this application all at once. Each of theseother performance data sets is represented by a row in this table (or other type of view). The status for adata set reflects the result of the last attempt to collect data for that data set, so you can see whether theagent is collecting data correctly. Unlike other data sets, the Performance Object Status data set does notreflect the state of the monitored application. This data set is most often used to determine why data isnot available for one of the performance data sets.


Average Collection DurationThe average duration of all data collections of this group in seconds. The type is real number(32-bit counter) with two decimal places of precision with enumerated values. The followingvalues are defined: NO DATA (-100). Any value that does not have a definition here is displayedin the User Interface.

The following names are defined for this attribute: AVERAGE_COLLECTION_DURATION orCOLAVGD (historical name), Average Collection Duration (caption), Average_Collection_Duration(attribute name), and COLAVGD (column name).

Cache Hit PercentThe percentage of external data requests for this group that were satisfied from the cache. Thetype is real number (32-bit counter) with two decimal places of precision.

The following names are defined for this attribute: CACHE_HIT_PERCENT or CACHPCT(historical name), Cache Hit Percent (caption), Cache_Hit_Percent (attribute name), andCACHPCT (column name).

Cache HitsThe number of times an external data request for this group was satisfied from the cache. Thetype is integer (32-bit counter).

The following names are defined for this attribute: CACHE_HITS or CACHEHT (historicalname), Cache Hits (caption), Cache_Hits (attribute name), and CACHEHT (column name).


Cache MissesThe number of times an external data request for this group was not available in the cache. Thetype is integer (32-bit counter).

The following names are defined for this attribute: CACHE_MISSES or CACHEMS (historicalname), Cache Misses (caption), Cache_Misses (attribute name), and CACHEMS (column name).

Error CodeThe error code associated with the query. The type is integer with enumerated values. Thefollowing values are defined: NO ERROR (0), GENERAL ERROR (1), OBJECT NOT FOUND (2),COUNTER NOT FOUND (3), NAMESPACE ERROR (4), OBJECT CURRENTLY UNAVAILABLE(5), COM LIBRARY INIT FAILURE (6), SECURITY INIT FAILURE (7), PROXY SECURITYFAILURE (9), NO INSTANCES RETURNED (10), ASSOCIATOR QUERY FAILED (11),REFERENCE QUERY FAILED (12), NO RESPONSE RECEIVED (13), CANNOT FIND JOINEDQUERY (14), CANNOT FIND JOIN ATTRIBUTE IN QUERY 1 RESULTS (15), CANNOT FINDJOIN ATTRIBUTE IN QUERY 2 RESULTS (16), QUERY 1 NOT A SINGLETON (17), QUERY 2NOT A SINGLETON (18), NO INSTANCES RETURNED IN QUERY 1 (19), NO INSTANCESRETURNED IN QUERY 2 (20), CANNOT FIND ROLLUP QUERY (21), CANNOT FIND ROLLUPATTRIBUTE (22), FILE OFFLINE (23), NO HOSTNAME (24), MISSING LIBRARY (25),ATTRIBUTE COUNT MISMATCH (26), ATTRIBUTE NAME MISMATCH (27), COMMON DATAPROVIDER NOT STARTED (28), CALLBACK REGISTRATION ERROR (29), MDL LOAD ERROR(30), AUTHENTICATION FAILED (31), CANNOT RESOLVE HOST NAME (32), SUBNODEUNAVAILABLE (33), SUBNODE NOT FOUND IN CONFIG (34), ATTRIBUTE ERROR (35),CLASSPATH ERROR (36), CONNECTION FAILURE (37), FILTER SYNTAX ERROR (38), FILENAME MISSING (39), SQL QUERY ERROR (40), SQL FILTER QUERY ERROR (41), SQL DBQUERY ERROR (42), SQL DB FILTER QUERY ERROR (43), PORT OPEN FAILED (44), ACCESSDENIED (45), TIMEOUT (46), NOT IMPLEMENTED (47), REQUESTED A BAD VALUE (48),RESPONSE TOO BIG (49), GENERAL RESPONSE ERROR (50), SCRIPT NONZERO RETURN(51), SCRIPT NOT FOUND (52), SCRIPT LAUNCH ERROR (53), CONF FILE DOES NOT EXIST(54), CONF FILE ACCESS DENIED (55), INVALID CONF FILE (56), EIF INITIALIZATIONFAILED (57), CANNOT OPEN FORMAT FILE (58), FORMAT FILE SYNTAX ERROR (59),REMOTE HOST UNAVAILABLE (60), EVENT LOG DOES NOT EXIST (61), PING FILE DOESNOT EXIST (62), NO PING DEVICE FILES (63), PING DEVICE LIST FILE MISSING (64), SNMPMISSING PASSWORD (65), DISABLED (66), URLS FILE NOT FOUND (67), XML PARSE ERROR(68), NOT INITIALIZED (69), ICMP SOCKETS FAILED (70), DUPLICATE CONF FILE (71),DELETED CONFIGURATION (72). Any value that does not have a definition here is displayed inthe User Interface.

The following names are defined for this attribute: ERROR_CODE or ERRCODE (historicalname), Error Code (caption), Error_Code (attribute name), and ERRCODE (column name).

Intervals SkippedThe number of times a background data collection for this group was skipped because theprevious collection was still running when the next one was due to start. The type is integer(32-bit counter).

The following names are defined for this attribute: INTERVALS_SKIPPED or INTSKIP (historicalname), Intervals Skipped (caption), Intervals_Skipped (attribute name), and INTSKIP (columnname).

Last Collection DurationThe duration of the most recently completed data collection of this group in seconds. The type isreal number (32-bit counter) with two decimal places of precision.

The following names are defined for this attribute: LAST_COLLECTION_DURATION orCOLDURA (historical name), Last Collection Duration (caption), Last_Collection_Duration(attribute name), and COLDURA (column name).

Last Collection FinishedThe most recent time a data collection of this group finished. The type is timestamp with


enumerated values. The following values are defined: NOT COLLECTED (0691231190000000),NOT COLLECTED (0000000000000001). Any value that does not have a definition here isdisplayed in the User Interface.

The following names are defined for this attribute: LAST_COLLECTION_FINISHED or COLFINI(historical name), Last Collection Finished (caption), Last_Collection_Finished (attribute name),and COLFINI (column name).

Last Collection StartThe most recent time a data collection of this group started. The type is timestamp withenumerated values. The following values are defined: NOT COLLECTED (0691231190000000),NOT COLLECTED (0000000000000001). Any value that does not have a definition here isdisplayed in the User Interface.

The following names are defined for this attribute: LAST_COLLECTION_START or COLSTRT(historical name), Last Collection Start (caption), Last_Collection_Start (attribute name), andCOLSTRT (column name).



Number of CollectionsThe number of data collections for this group since the agent started. The type is integer (32-bitcounter).

The following names are defined for this attribute: NUMBER_OF_COLLECTIONS or NUMCOLL(historical name), Number of Collections (caption), Number_of_Collections (attribute name), andNUMCOLL (column name).

Object NameThe name of the performance object. The type is string.

The following names are defined for this attribute: OBJECT_NAME or OBJNAME (historicalname), Object Name (caption), Object_Name (attribute name), and OBJNAME (column name).

Object StatusThe status of the performance object. The type is integer with enumerated values. The followingvalues are defined: ACTIVE (0), INACTIVE (1). Any value that does not have a definition here isdisplayed in the User Interface.

The following names are defined for this attribute: OBJECT_STATUS or OBJSTTS (historicalname), Object Status (caption), Object_Status (attribute name), and OBJSTTS (column name).

Object TypeThe type of the performance object. The type is integer with enumerated values. The followingvalues are defined: WMI (0), PERFMON (1), WMI ASSOCIATION GROUP (2), JMX (3), SNMP(4), SHELL COMMAND (5), JOINED GROUPS (6), CIMOM (7), CUSTOM (8), ROLLUP DATA (9),WMI REMOTE DATA (10), LOG FILE (11), JDBC (12), CONFIG DISCOVERY (13), NT EVENTLOG (14), FILTER (15), SNMP EVENT (16), PING (17), DIRECTOR DATA (18), DIRECTOREVENT (19), SSH REMOTE SHELL COMMAND (20). Any value that does not have a definitionhere is displayed in the User Interface.

The following names are defined for this attribute: OBJECT_TYPE or OBJTYPE (historical name),Object Type (caption), Object_Type (attribute name), and OBJTYPE (column name).

Query NameThe name of the attribute group. This attribute is a key attribute. The type is string.

The following names are defined for this attribute: QUERY_NAME or ATTRGRP (historicalname), Query Name (caption), Query_Name (attribute name), and ATTRGRP (column name).


Refresh IntervalThe interval at which this group is refreshed in seconds. The type is integer (32-bit counter).

The following names are defined for this attribute: REFRESH_INTERVAL or REFRINT (historicalname), Refresh Interval (caption), Refresh_Interval (attribute name), and REFRINT (columnname).



Server Info data setSoftware server information for OSLC. A data sample is sent to the server every 60 minutes and ismaintained for 8 days by default.


Database NameName of the database. This attribute is a key attribute. The type is string.


FQDN Fully qualified domain name of this server. This attribute is a key attribute. The type is string.

The following names are defined for this attribute: FQDN (historical name), FQDN (caption),FQDN (attribute name), and FQDN (column name).

HostnameShort host name of this server. This attribute is a key attribute. The type is string.

The following names are defined for this attribute: HOSTNAME (historical name), Hostname(caption), Hostname (attribute name), and HOSTNAME (column name).

IP AddressIP address of this server. This attribute is a key attribute. The type is string.

The following names are defined for this attribute: IP_ADDRESS or IPADDR (historical name), IPAddress (caption), IP_Address (attribute name), and IPADDR (column name).



Port TCP port for this server. This attribute is a key attribute. The type is integer (32-bit numericproperty).

The following names are defined for this attribute: PORT (historical name), Port (caption), Port(attribute name), and PORT (column name).



SQL Response Time data setThe response time of the SQL statement in milliseconds. A data sample is sent to the server every minuteand is maintained for 8 days by default.



Db NameThe database name. This attribute is a key attribute. The type is string.

The following names are defined for this attribute: DB_NAME or DBNAME (historical name), DbName (caption), Db_Name (attribute name), and DBNAME (column name).



SQL Response TimeThe response time of the SQL statement in milliseconds. The type is real number (64-bit gauge)with two decimal places of precision.

The following names are defined for this attribute: SQL_RESPONSE_TIME or RESPTIME(historical name), SQL Response Time (caption), SQL_Response_Time (attribute name), andRESPTIME (column name).



SQL Statement Perf data setThe performance of SQL statements. A data sample is sent to the server every minute and is maintainedfor 8 days by default.


Affect RowsThe rows that are affected by the SQL statement. The type is integer (64-bit counter).

The following names are defined for this attribute: AFFECT_ROWS or AFFECTROW (historicalname), Affect Rows (caption), Affect_Rows (attribute name), and AFFECTROW (column name).

Database NameThe database name. This attribute is a key attribute. The type is string.


Exec TimeThe execution time of the SQL statement in milliseconds. The type is integer (64-bit gauge).

The following names are defined for this attribute: EXEC_TIME or EXECTIME (historical name),Exec Time (caption), Exec_Time (attribute name), and EXECTIME (column name).



SQL TextThe SQL statement. This attribute is a key attribute. The type is string.

The following names are defined for this attribute: SQL_TEXT or SQLTEXT (historical name), SQLText (caption), SQL_Text (attribute name), and SQLTEXT (column name).




Query InfoThe database name and the SQL query. The type is string.

The following names are defined for this attribute: QUERY_INFO or QUERYINFO (historicalname), Query Info (caption), Query_Info (attribute name), and QUERYINFO (column name).

Take Action Status data setThe Take Action Status data set contains information about the results of actions this agent ran.


Action App Return CodeThe application return code of the action is the actual return code of the command run. The typeis integer (32-bit numeric property).

The following names are defined for this attribute: ACTION_APP_RETURN_CODE or TSKAPRC(historical name), Action App Return Code (caption), Action_App_Return_Code (attribute name),and TSKAPRC (column name).

Action CommandThe command that was run by the action. The type is string.

The following names are defined for this attribute: ACTION_COMMAND or TSKCMND(historical name), Action Command (caption), Action_Command (attribute name), andTSKCMND (column name).

Action IDThe id of the action. The type is integer (32-bit numeric property).

The following names are defined for this attribute: ACTION_ID or TSKID (historical name),Action ID (caption), Action_ID (attribute name), and TSKID (column name).

Action InstanceThe instance that is associated with the output produced by running the action. The type isstring.

The following names are defined for this attribute: ACTION_INSTANCE or TSKINST (historicalname), Action Instance (caption), Action_Instance (attribute name), and TSKINST (column name).

Action MessageThe message that is associated with the return code of the action. The type is string.

The following names are defined for this attribute: ACTION_MESSAGE or TSKMSGE (historicalname), Action Message (caption), Action_Message (attribute name), and TSKMSGE (columnname).

Action NameThe name of the action that was run. The type is string.

The following names are defined for this attribute: ACTION_NAME or TSKNAME (historicalname), Action Name (caption), Action_Name (attribute name), and TSKNAME (column name).

Action NodeThe node where the action ran. The type is string.

The following names are defined for this attribute: ACTION_NODE or TSKORGN (historicalname), Action Node (caption), Action_Node (attribute name), and TSKORGN (column name).

Action OwnerThe name of the situation or user that initiated the action. The type is string.


The following names are defined for this attribute: ACTION_OWNER or TSKOWNR (historicalname), Action Owner (caption), Action_Owner (attribute name), and TSKOWNR (column name).

Action ResultsThe output that is produced by running the action. The type is string.

The following names are defined for this attribute: ACTION_RESULTS or TSKOUTP (historicalname), Action Results (caption), Action_Results (attribute name), and TSKOUTP (column name).

Action StatusThe return code from the Action Status dialog, which is the return code category that is definedfor the application return code. The type is integer (32-bit numeric property).

The following names are defined for this attribute: ACTION_STATUS or TSKSTAT (historicalname), Action Status (caption), Action_Status (attribute name), and TSKSTAT (column name).

Action SubnodeThe subnode where the action ran. The type is string.

The following names are defined for this attribute: ACTION_SUBNODE or TSKSBND (historicalname), Action Subnode (caption), Action_Subnode (attribute name), and TSKSBND (columnname).

Action TypeThe type of the action. The type is integer (32-bit numeric property) with enumerated values. Thefollowing values are defined: UNKNOWN (0), AUTOMATION (1). Any value that does not havea definition here is displayed in the User Interface.

The following names are defined for this attribute: ACTION_TYPE or TSKTYPE (historical name),Action Type (caption), Action_Type (attribute name), and TSKTYPE (column name).



TimestampThe time the event was generated. The type is string.


Thread Pool Status data setThe Thread Pool Status data set contains information that reflects the status of the internal thread poolused to collect data asynchronously.




Thread Pool Active ThreadsThe number of threads in the thread pool currently active doing work. The type is integer (32-bitgauge) with enumerated values. The following values are defined: NO DATA (-1), NO DATA(-100). Any value that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: THREAD_POOL_ACTIVE_THREADS orTPACTTH (historical name), Thread Pool Active Threads (caption), Thread_Pool_Active_Threads(attribute name), and TPACTTH (column name).

Thread Pool Avg Active ThreadsThe average number of threads in the thread pool simultaneously active doing work. The type is


real number (32-bit gauge) with two decimal places of precision with enumerated values. Thefollowing values are defined: NO DATA (-1), NO DATA (-100). Any value that does not have adefinition here is displayed in the User Interface.

The following names are defined for this attribute: THREAD_POOL_AVG_ACTIVE_THREADS orTPAVGAT (historical name), Thread Pool Avg Active Threads (caption),Thread_Pool_Avg_Active_Threads (attribute name), and TPAVGAT (column name).

Thread Pool Avg Job WaitThe average time a job spends waiting on the thread pool queue in seconds. The type is realnumber (32-bit gauge) with two decimal places of precision with enumerated values. Thefollowing values are defined: NO DATA (-1), NO DATA (-100). Any value that does not have adefinition here is displayed in the User Interface.

The following names are defined for this attribute: THREAD_POOL_AVG_JOB_WAIT orTPAVJBW (historical name), Thread Pool Avg Job Wait (caption), Thread_Pool_Avg_Job_Wait(attribute name), and TPAVJBW (column name).

Thread Pool Avg Queue LengthThe average length of the thread pool queue during this run. The type is real number (32-bitgauge) with two decimal places of precision with enumerated values. The following values aredefined: NO DATA (-1), NO DATA (-100). Any value that does not have a definition here isdisplayed in the User Interface.

The following names are defined for this attribute: THREAD_POOL_AVG_QUEUE_LENGTH orTPAVGQL (historical name), Thread Pool Avg Queue Length (caption),Thread_Pool_Avg_Queue_Length (attribute name), and TPAVGQL (column name).

Thread Pool Max Active ThreadsThe peak number of threads in the thread pool that were simultaneously active doing work. Thetype is integer (32-bit counter) with enumerated values. The following values are defined: NODATA (-1), NO DATA (-100). Any value that does not have a definition here is displayed in theUser Interface.

The following names are defined for this attribute: THREAD_POOL_MAX_ACTIVE_THREADSor TPMAXAT (historical name), Thread Pool Max Active Threads (caption),Thread_Pool_Max_Active_Threads (attribute name), and TPMAXAT (column name).

Thread Pool Max Queue LengthThe peak length the thread pool queue reached. The type is integer (32-bit counter) withenumerated values. The following values are defined: NO DATA (-1), NO DATA (-100). Anyvalue that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: THREAD_POOL_MAX_QUEUE_LENGTH orTPMAXQL (historical name), Thread Pool Max Queue Length (caption),Thread_Pool_Max_Queue_Length (attribute name), and TPMAXQL (column name).

Thread Pool Max SizeThe maximum number of threads that are allowed to exist in the thread pool. The type is integer(32-bit numeric property) with enumerated values. The following values are defined: NO DATA(-1), NO DATA (-100). Any value that does not have a definition here is displayed in the UserInterface.

The following names are defined for this attribute: THREAD_POOL_MAX_SIZE or TPMAXSZ(historical name), Thread Pool Max Size (caption), Thread_Pool_Max_Size (attribute name), andTPMAXSZ (column name).

Thread Pool Min Active ThreadsThe smallest number of threads in the thread pool that were simultaneously active doing work.The type is integer (32-bit counter) with enumerated values. The following values are defined:NO DATA (-1), NO DATA (-100). Any value that does not have a definition here is displayed inthe User Interface.


The following names are defined for this attribute: THREAD_POOL_MIN_ACTIVE_THREADS orTPMINAT (historical name), Thread Pool Min Active Threads (caption),Thread_Pool_Min_Active_Threads (attribute name), and TPMINAT (column name).

Thread Pool Min Queue LengthThe minimum length the thread pool queue reached. The type is integer (32-bit counter) withenumerated values. The following values are defined: NO DATA (-1), NO DATA (-100). Anyvalue that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: THREAD_POOL_MIN_QUEUE_LENGTH orTPMINQL (historical name), Thread Pool Min Queue Length (caption),Thread_Pool_Min_Queue_Length (attribute name), and TPMINQL (column name).

Thread Pool Queue LengthThe number of jobs currently waiting in the thread pool queue. The type is integer (32-bit gauge)with enumerated values. The following values are defined: NO DATA (-1), NO DATA (-100). Anyvalue that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: THREAD_POOL_QUEUE_LENGTH orTPQLGTH (historical name), Thread Pool Queue Length (caption), Thread_Pool_Queue_Length(attribute name), and TPQLGTH (column name).

Thread Pool SizeThe number of threads currently existing in the thread pool. The type is integer (32-bit gauge)with enumerated values. The following values are defined: NO DATA (-1), NO DATA (-100). Anyvalue that does not have a definition here is displayed in the User Interface.

The following names are defined for this attribute: THREAD_POOL_SIZE or THPSIZE (historicalname), Thread Pool Size (caption), Thread_Pool_Size (attribute name), and THPSIZE (columnname).

Thread Pool Total JobsThe number of jobs that are completed by all threads in the pool since agent start. The type isinteger (32-bit counter) with enumerated values. The following values are defined: NO DATA (-1),NO DATA (-100). Any value that does not have a definition here is displayed in the UserInterface.

The following names are defined for this attribute: THREAD_POOL_TOTAL_JOBS or TPTJOBS(historical name), Thread Pool Total Jobs (caption), Thread_Pool_Total_Jobs (attribute name), andTPTJOBS (column name).





Accessibility features

Accessibility features assist users who have a disability, such as restricted mobility or limited vision, touse information technology content successfully.

Accessibility features

The web-based interface of IBM® Cloud Application Performance Management is the Cloud APMconsole. The console includes the following major accessibility features:v Enables users to use assistive technologies, such as screen-reader software and digital speech

synthesizer, to hear what is displayed on the screen.1 Consult the product documentation of theassistive technology for details on using those technologies with this product.

v Enables users to operate specific or equivalent features using only the keyboard.v Communicates all information independently of color.2

The Cloud APM console uses the latest W3C Standard, WAI-ARIA 1.0, US Section 508, and Web ContentAccessibility Guidelines (WCAG) 2.0. To take advantage of accessibility features, use the latest release ofyour screen reader in combination with the latest web browser that is supported by this product.

The Cloud APM console online product documentation in IBM Knowledge Center is enabled foraccessibility. The accessibility features of IBM Knowledge Center are described at IBM Knowledge Centerrelease notes.

Keyboard navigation

This product uses standard navigation keys.

Interface information

The Cloud APM console web user interface does not rely on cascading style sheets to render contentproperly and to provide a usable experience. However, the product documentation does rely oncascading style sheets. IBM Knowledge Center provides an equivalent way for low-vision users to usetheir custom display settings, including high-contrast mode. You can control font size by using the deviceor browser settings.

The Cloud APM console web user interface includes WAI-ARIA navigational landmarks that you can useto quickly navigate to functional areas in the application.

The Cloud APM console user interface does not have content that flashes 2 - 55 times per second.

Related accessibility information

In addition to standard IBM help desk and support websites, IBM has established a TTY telephoneservice for use by deaf or hard of hearing customers to access sales and support services:

TTY service 800-IBM-3383 (800-426-3383) (within North America)

1. Exceptions include some of the Agent Configuration pages and historical line charts in the Cloud APM console.

2. Exceptions include some Agent Configuration pages of the Cloud APM console.


http://www.w3.org/TR/wai-aria/

http://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards

http://www.w3.org/TR/WCAG20/

http://www.w3.org/TR/WCAG20/

http://www.ibm.com/support/knowledgecenter/en/about/releasenotes.html?view=kc#accessibility

http://www.ibm.com/support/knowledgecenter/en/about/releasenotes.html?view=kc#accessibility

IBM and accessibility

For more information about the commitment that IBM has to accessibility, see IBM Accessibility .


http://www.ibm.com/able

Notices

This information was developed for products and services offered in the US. This material might beavailable from IBM in other languages. However, you may be required to own a copy of the product orproduct version in that language in order to access it.

IBM may not offer the products, services, or features discussed in this document in other countries.Consult your local IBM representative for information on the products and services currently available inyour area. Any reference to an IBM product, program, or service is not intended to state or imply thatonly that IBM product, program, or service may be used. Any functionally equivalent product, program,or service that does not infringe any IBM intellectual property right may be used instead. However, it isthe user's responsibility to evaluate and verify the operation of any non-IBM product, program, orservice.

IBM may have patents or pending patent applications covering subject matter described in thisdocument. The furnishing of this document does not grant you any license to these patents. You can sendlicense inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM IntellectualProperty Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY ORFITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication.IBM may make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not inany manner serve as an endorsement of those websites. The materials at those websites are not part ofthe materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide in any way it believes appropriate withoutincurring any obligation to you.


Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

Such information may be available, subject to appropriate terms and conditions, including in some cases,payment of a fee.

The licensed program described in this document and all licensed material available for it are providedby IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement orany equivalent agreement between us.

The performance data discussed herein is presented as derived under specific operating conditions.Actual results may vary.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related tonon-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

Statements regarding IBM's future direction or intent are subject to change or withdrawal without notice,and represent goals and objectives only.

This information is for planning purposes only. The information herein is subject to change before theproducts described become available.

This information contains examples of data and reports used in daily business operations. To illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to actual people or business enterprises isentirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programsin any form without payment to IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for the operating platform forwhich the sample programs are written. These examples have not been thoroughly tested under allconditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative workmust include a copyrightnotice as follows:© (your company name) (year).Portions of this code are derived from IBM Corp. Sample Programs.© Copyright IBM Corp. 2014, 2015.


TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the web at"Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in theUnited States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/orits affiliates.

Terms and conditions for product documentationPermissions for the use of these publications are granted subject to the following terms and conditions.

Applicability

These terms and conditions are in addition to any terms of use for the IBM website.

Personal use

You may reproduce these publications for your personal, noncommercial use provided that allproprietary notices are preserved. You may not distribute, display or make derivative work of thesepublications, or any portion thereof, without the express consent of IBM.

Commercial use

You may reproduce, distribute and display these publications solely within your enterprise provided thatall proprietary notices are preserved. You may not make derivative works of these publications, orreproduce, distribute or display these publications or any portion thereof outside your enterprise, withoutthe express consent of IBM.

Rights

Except as expressly granted in this permission, no other permissions, licenses or rights are granted, eitherexpress or implied, to the publications or any information, data, software or other intellectual propertycontained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use ofthe publications is detrimental to its interest or, as determined by IBM, the above instructions are notbeing properly followed.

You may not download, export or re-export this information except in full compliance with all applicablelaws and regulations, including all United States export laws and regulations.

Notices 37

http://www.ibm.com/legal/us/en/copytrade.shtml

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THEPUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OFMERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

IBM Online Privacy StatementIBM Software products, including software as a service solutions, (“Software Offerings”) may use cookiesor other technologies to collect product usage information, to help improve the end user experience, totailor interactions with the end user or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offerings can help enable you tocollect personally identifiable information. If this Software Offering uses cookies to collect personallyidentifiable information, specific information about this offering's use of cookies is set forth in thefollowing paragraphs.

Depending upon the configurations deployed, this Software Offering may use session cookies that collecteach user's user name for purposes of session management, authentication, and single sign-onconfiguration. These cookies can be disabled, but disabling them will also likely eliminate thefunctionality they enable.

If the configurations deployed for this Software Offering provide you as customer the ability to collectpersonally identifiable information from end users via cookies and other technologies, you should seekyour own legal advice about any laws applicable to such data collection, including any requirements fornotice and consent.

For more information about the use of various technologies, including cookies, for these purposes, SeeIBM's Privacy Policy at http://www.ibm.com/privacy and IBM's Online Privacy Statement athttp://www.ibm.com/privacy/details the section entitled “Cookies, Web Beacons and OtherTechnologies” and the “IBM Software Products and Software-as-a-Service Privacy Statement” athttp://www.ibm.com/software/info/product-privacy.


http://www.ibm.com/privacy

http://www.ibm.com/privacy/details

http://www.ibm.com/software/info/product-privacy

Index

Aaccessibility features 33Action App Return Code attribute 28Action Command attribute 28Action ID attribute 28Action Instance attribute 28Action Message attribute 28Action Name attribute 28Action Node attribute 28Action Owner attribute 28Action Results attribute 29Action Status attribute 29Action Subnode attribute 29Action Type attribute 29Active Db Num attribute 19additional information

attributes 11Affect Rows attribute 27Application Availability data set 13Application Component attribute 14attributes

Action App Return Code 28Action Command 28Action ID 28Action Instance 28Action Message 28Action Name 28Action Node 28Action Owner 28Action Results 29Action Status 29Action Subnode 29Action Type 29Active Db Num 19Affect Rows 27Application Availability 13Application Component 14Availability 14Average Collection Duration 23Buffer Hit Percent 18Buffer Hit Percentage 18Cache Hit Percent 23Cache Hits 23Cache Misses 24Command Line 14Connection Num 16CPU Value 19Database Name 17, 18, 20, 21, 26, 27Database Query Counts 17Db Allow Conn 18Db Buff Hit Rate 18Db CPU 19Db Memory 19Db Name 27Db Num 19DB Size 20Delete SQL Count 17Error Code 24Exec Time 27FQDN 26Full Name 14

attributes (continued)Functionality Test Message 14Functionality Test Status 14Hold App Name 22Hold PID 21Hold SQL 21Hostname 26Inactive Db Num 20Insert SQL Count 17Intervals Skipped 24IP Address 26Last Collection Duration 24Last Collection Finished 24Last Collection Start 25Lock Detail 21Lock Mode 21Lock Sum 22, 23Lock Type 21Lock Type ID 21Locks 22Locks Filter 22Locks v96 23Memory 19Name 15Node 13, 15, 16, 17, 18, 19, 20, 21, 22, 23, 25, 26, 27, 29Number Active Connections 18Number of Collections 25Object Name 25Object Status 25Object Type 25overview 11Page Faults per Sec 15Percent Privileged Time 15Percent Processor Time 15Percent User Mode Time 15Performance Object Status 23PID 15Port 26Query Info 28Query Name 25Refresh Interval 26Select SQL Count 17Server Info 26SQL Response Time 27SQL Statement Perf 27SQL Text 27Status 13, 15Table Space Name 20Table Space Size MB 20Take Action Status 28Thread Count 16Thread Pool Active Threads 29Thread Pool Avg Active Threads 29Thread Pool Avg Job Wait 30Thread Pool Avg Queue Length 30Thread Pool Max Active Threads 30Thread Pool Max Queue Length 30Thread Pool Max Size 30Thread Pool Min Active Threads 30Thread Pool Min Queue Length 31Thread Pool Queue Length 31


attributes (continued)Thread Pool Size 31Thread Pool Status 29Thread Pool Total Jobs 31Timestamp 14, 16, 17, 18, 19, 20, 21, 22, 23, 26, 27, 29, 31Total Count 17Type 16Update SQL Count 17Virtual Size 16Wait App Name 22Wait PID 21Wait Time 21Working Set Size 16

Availability data set 14Average Collection Duration attribute 23

BBuffer Hit Percent attribute 18Buffer Hit Percentage attribute 18

CCache Hit Percent attribute 23Cache Hits attribute 23Cache Misses attribute 24Command Line attribute 14Connection Num attribute 16Connection Num data set 16CPU Value attribute 19

Ddashboard 3data set

attributes 13data sets

Application Availability 13Availability 14Connection Num 16Database Query Counts 17Db Buff Hit Rate 18Db CPU 19Db Memory 19Db Num 19DB Size 20list of all 12Lock Detail 21Locks 22Locks Filter 22Locks v96 23overview 11Performance Object Status 23Server Info 26SQL Response Time 27SQL Statement Perf 27Take Action Status 28Thread Pool Status 29

Database Name attribute 17, 18, 20, 21, 26, 27Database Query Counts data set 17Db Allow Conn attribute 18Db Buff Hit Rate data set 18Db CPU data set 19Db Memory data set 19Db Name attribute 27Db Num data set 19

DB Size data set 20Delete SQL Count attribute 17

EError Code attribute 24Exec Time attribute 27

FFQDN attribute 26Full Name attribute 14Functionality Test Message attribute 14Functionality Test Status attribute 14

HHold App Name attribute 22Hold PID attribute 21Hold SQL attribute 21Hostname attribute 26

IInactive Db Num attribute 20Insert SQL Count attribute 17Intervals Skipped attribute 24Introduction 1IP Address attribute 26

KKPIs 3

LLast Collection Duration attribute 24Last Collection Finished attribute 24Last Collection Start attribute 25Lock Detail data set 21Lock Mode attribute 21Lock Sum attribute 22, 23Lock Type attribute 21Lock Type ID attribute 21Locks data set 22Locks Filter data set 22Locks v96 data set 23

MMemory attribute 19

NName attribute 15Node attribute 13, 15, 16, 17, 18, 19, 20, 21, 22, 23, 25, 26, 27,

29Number Active Connections attribute 18Number of Collections attribute 25


OObject Name attribute 25Object Status attribute 25Object Type attribute 25

PPage Faults per Sec attribute 15Percent Privileged Time attribute 15Percent Processor Time attribute 15Percent User Mode Time attribute 15Performance Object Status data set 23PID attribute 15Port attribute 26

QQuery Info attribute 28Query Name attribute 25

RRefresh Interval attribute 26

SSelect SQL Count attribute 17Server Info data set 26SQL Response Time attribute 27SQL Response Time data set 27SQL Statement Perf data set 27SQL Text attribute 27Status attribute 13, 15

TTable Space Name attribute 20Table Space Size MB attribute 20Take Action Status data set 28Thread Count attribute 16Thread Pool Active Threads attribute 29Thread Pool Avg Active Threads attribute 29Thread Pool Avg Job Wait attribute 30Thread Pool Avg Queue Length attribute 30Thread Pool Max Active Threads attribute 30Thread Pool Max Queue Length attribute 30Thread Pool Max Size attribute 30Thread Pool Min Active Threads attribute 30Thread Pool Min Queue Length attribute 31Thread Pool Queue Length attribute 31Thread Pool Size attribute 31Thread Pool Status data set 29Thread Pool Total Jobs attribute 31thresholds 7thresholds, using attributes 11Timestamp attribute 14, 16, 17, 18, 19, 20, 21, 22, 23, 26, 27,

29, 31Total Count attribute 17Type attribute 16

UUpdate SQL Count attribute 17

VVirtual Size attribute 16

WWait App Name attribute 22Wait PID attribute 21Wait Time attribute 21widgets 3Working Set Size attribute 16

Index 41


IBM®

Printed in USA

Documents

IBM · Overview tab show Postgr eSQL in the Components gr oup: v Click Components to see a single Postgr eSQL gr oup widget that is displayed along with a gr oup widget for every