CA Unified Infrastructure Management

Transcription

1 CA Unified Infrastructure Management Probe Guide for Informix Database Monitoring informix v4.1 series

2 Copyright Notice This online help system (the "System") is for your informational purposes only and is subject to change or withdrawal by CA at any time. This System may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This System is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties. This System may not be disclosed by you or used for any purpose other than as may be permitted in a separate agreement between you and CA governing your use of the CA software to which the System relates (the CA Software ). Such agreement is not modified in any way by the terms of this notice. Notwithstanding the foregoing, if you are a licensed user of the CA Software you may make one copy of the System for internal use by you and your employees, provided that all CA copyright notices and legends are affixed to the reproduced copy. The right to make a copy of the System is limited to the period during which the license for the CA Software remains in full force and effect. Should the license terminate for any reason, it shall be your responsibility to certify in writing to CA that all copies and partial copies of the System have been destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS SYSTEM AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS SYSTEM, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The manufacturer of this System is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. Copyright 2014 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Legal information on third-party and public domain software used in this product is documented in the Third-Party Licenses and Terms of Use (

3 Contact CA Contact CA Support For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At you can access the following resources: Online and telephone contact information for technical assistance and customer services Information about user communities and forums Product and documentation downloads CA Support policies and guidelines Other helpful resources appropriate for your product Providing Feedback about Product Documentation Send comments or questions about CA Technologies product documentation to To provide feedback about general CA Technologies product documentation, complete our short customer survey which is available on the support website at

4

5 Contents Chapter 1: Informix Database Monitoring (informix) Overview v4.1 7 About This Guide... 9 Related Documentation... 9 Preconfiguration Requirements... 9 Prerequisites Supported Platforms informix Installation notes for Windows Installation notes for Unix Chapter 2: Configuration Details 13 informix Node Checkpoints Node Configure A Node Create Connection Add Profile Checkpoints Delete Connection Add Profile Delete Profile Chapter 3: QoS Threshold Metrics 25 QoS Metrics Alert Metrics Default Settings Checkpoints metrics Single counter description Contents 5

6 Documentation Changes This table describes the version history for this document. Version Date What's New? 4.1 December 2013 Documentation on the initial web-based GUI version of the Informix Database Monitoring probe. (Previous versions of this probe are configured using Infrastructure Manager). 6 Probe Guide for Informix Database Monitoring

7 Chapter 1: Informix Database Monitoring (informix) Overview v4.1 The Informix Database Monitoring (informix) probe runs selected SQL queries to extract vital information about your Informix databases. The information is presented to the database administrator as alarms or as a report. The Informix Database Monitoring probe monitors the following information: Connectivity to the database server Uptime (in days) of the database server Number of databases Logging status of the databases Number of active users Databases for offline status Database for recovering status Database for redundancy Database mirror is offline Database mirror is recovering Chapter 1: Informix Database Monitoring (informix) Overview v4.1 7

8 About This Guide Database free space (percent) Database free space (MB) Buffer cache hit ratio for reads Buffer cache hit ratio for writes Table extents Table size (MB) Number of attempts exceeding the maximum number of locks Number of attempts exceeding the maximum number of threads Number of failed attempts allocating entries in the transaction table Number of times threads had to wait for a latch Number of times threads had to wait for a buffer Number of times sessions had to wait for a lock Number of times threads had to wait for critical section checkpoints Number of times potential deadlocks are detected and prevented Number of times distributed deadlock timeout is exceeded while user is waiting for lock Number of foreground writes Number of LRU writes Number of chunk writes Number of users waiting for locks Users waiting for locks Chunk I/O read statistics Chunk I/O write statistics Virtual cpu user time Virtual cpu system time This section contains the following topics: About This Guide (see page 9) Related Documentation (see page 9) Preconfiguration Requirements (see page 9) 8 Probe Guide for Informix Database Monitoring

9 About This Guide About This Guide This guide is for the CA Unified Infrastructure Management Administrator to help understand the configuration of the Informix Database Monitoring probe and provides the following information: Overview of the Informix Database Monitoring probe and related documentation for previous probe versions. Configuration details of the probe. Field information and common procedures for configuring the probe. Note: Description for the intuitive GUI fields is not included in the document. Related Documentation For related information, see the following material: Related Documentation Documentation for other versions of the informix probe The Release Notes for the informix probe User documentation for the Admin Console Monitor Metrics Reference Information for CA Unified Infrastructure Management Probes ( Preconfiguration Requirements This section contains the following preconfiguration requirements for the Informix Database Monitoring probe: Software: Informix Connect 3.50, Informix Client SDK 3.50 (or higher) and Informix 9.x, 10.x, 11.5, 11.7 Platforms: Windows 32/64 bit, Linux 32/64 bit, Solaris 8 and higher on Sparc 32/64 bit, Solaris on Amd 64 and i386 Hardware: Windows NT/2000/XP/2003/2008 Chapter 1: Informix Database Monitoring (informix) Overview v4.1 9

10 Preconfiguration Requirements Prerequisites This section contains the prerequisites for the Informix Database Monitoring probe: The Informix client or server is installed. Navigate to Run > Services.msc and restart the Nimsoft Robot Watcher service. Important! You cannot configure the informix probe in case the preceding prerequisites are not met. Supported Platforms Refer to the Compatibility Support Matrix for the latest information on supported platforms. See also the Support Matrix for Probes for information on the informix probe. informix Installation notes for Windows Informix Connect or the Client SDK (which contains Informix Connect too) must be installed before installing this probe. Refer to the installation documentation for the Client SDK or Informix Connect for information on how to install the Client SDK. Informix Connect or the Client SDK must be in the systems PATH environment variable. Run the setnet32 application for Informix for setting up connectivity with the databases you wish to monitor. Do not check the Use my settings checkbox in setnet32. The following keys exist in the Windows Registry for the probe to be able to connect: HKEY_LOCAL_MACHINE\Software\Informix\Environment\INFORMIXSERVER HKEY_LOCAL_MACHINE\Software\Informix\Environment\INFORMIXDIR HKEY_LOCAL_MACHINE\Software\Informix\SqlHosts\[one entry for each database] Setnet32 creates these keys if the Use my settings checkbox is unchecked, otherwise they are created under HKEY_CURRENT_USER. The dbping utility which is also a part of Informix Connect and the Client SDK allows you to test connections set up with setnet32. Verify a database connection definition by running this utility. Note: Database definition names are case-sensitive. Check the definition in setnet32 or the Windows Registry before setting up a profile in the probe. The user configured in the connection parameters must have CONNECT privileges on the Informix database server. The target database selected for connection must be sysmaster for the predefined checkpoints to work. 10 Probe Guide for Informix Database Monitoring

11 Preconfiguration Requirements Installation notes for Unix Informix Client SDK 3.5 must be installed in unix platform before installing this probe on that unix machine. Informix server can be connected Either ODBC DSN connection OR providing user, password, database, service, hostname information through informix GUI. The following Environment Variables are required for connecting with Informix Server: Set the INFORMIXDIR variable to the directory where you installed the informix Client SDK.eg. export INFORMIXDIR=/opt/IBM/informix. set LD_LIBRARY_PATH variable with informix client libraries path.eg. export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/IBM/informix/lib/cli:/opt/IBM/informi x/lib/esql. Set ODBCINI variable to odbc.ini file path. odbc.ini file keeps ODBC DSN connection information for informix.eg. export ODBCINI=/opt/IBM/informix/etc/odbc.ini You have to create the ODBC DSN connection. Follow these steps: 1. The service name for Informix database is defined in /etc/services configuration file. For example, testinformix 6605/tcp. 2. Add a line in $INFORMIXDIR/etc/sqlhosts file for Informix databases server. Each line in Sqlhosts file contains server, protocol, hostname, service/port information for the database server. For example, informix server onsoctcp Add new ODBC DSN entry in $INFORMIXDIR/etc/odbc.ini file as follows: [testdb] Driver=/opt/IBM/informix/lib/cli/iclis09b.so Description= IBM INFORMIX ODBC DRIVER Server=informixserver Database=sysmaster LogonID=Informix pwd=redhat CLIENT_LOCALE=en_us DB_LOCALE=en_us TRANSLATIONDLL=/opt/IBM/informix/lib/esql/igo4a304.so Chapter 1: Informix Database Monitoring (informix) Overview v4.1 11

12

13 Chapter 2: Configuration Details The initial configuration of the Informix Database Monitoring probe is done by using the configuration tool (GUI), setting up one or more database instance profiles. The probe either runs locally on the database server, or it runs as a remote client. This section contains the following topics: informix Node (see page 14) Configure A Node (see page 22) Create Connection (see page 22) Add Profile Checkpoints (see page 22) Delete Connection (see page 23) Add Profile (see page 23) Delete Profile (see page 23) Chapter 2: Configuration Details 13

14 informix Node informix Node This node lets you view and configure the details of Informix Database Monitoring probe. You can also configure the log properties of the probe and list of alarm messages that are defined on the Informix Database Monitoring probe. Navigation: informix Set or modify the following values as required: informix > Probe Information This section provides information about the probe name, probe version, start time of the probe, and the vendor who created the probe. informix > General Config This section lets you configure the QoS and log properties of the Informix Database Monitoring probe. Alarm Severity Filter: Specifies a filter on severity level of an event for considering an event as an alarm. Log Size: Specifies the size of the log file that stores the internal messages of the probe. Log Level: Specifies the level of details that the probe log file saves. QoS V2 Compatibility: Generates suppression key in the alarm message. Default: Not selected informix > Message Pool This section enables you to view the list of all the alarm messages available for the Informix Database Monitoring probe. 14 Probe Guide for Informix Database Monitoring

15 informix Node Checkpoints Node This node enables you to create a checkpoint defined for a number of profiles. For some of the checkpoints, defaults setting are applied. Navigation: informix > Checkpoints Set or modify the following values as required: Checkpoints > Create New Checkpoint This section lets you create a checkpoint with default settings or user-configurable settings. Connection Name: Specifies the connection that the profile monitors. Query File: Defines the file that stores the query. Query: Defines the query that the checkpoint reads. Interval Modus: Enables you to configure the interval value of the checkpoint. Note: The interval value is the difference between the results of two queries. Chapter 2: Configuration Details 15

16 informix Node <Checkpoint Name> Node This node lets you configure the checkpoint properties such as message, objects, and monitoring conditions. Note: This node is user-configurable and is called checkpoint name node in the document. Navigation: informix > Checkpoints > checkpoint name Set or modify the following values as required: checkpoint name > General Config This node lets you configure the properties of the checkpoint. Check Point Name: Specifies the available checkpoints name. Active: Activates the checkpoint. Description: Defines a short description of the checkpoint. Condition: Specifies how the information is transmitted. Check Interval: Specifies the default value of the check interval in the checkpoint. Samples: Specifies the number of samples used for calculating the average value. Default: 1 Clear Severity: Specifies the severity of the clear message. Clear Message: Specifies the clear message name. Use Exclude/Use Include: Adds the objects to the exclude/include list of some of the checkpoints. Enable Exclude: Specifies the checkpoint objects that you do not want to monitor. Enable Include: Specifies the checkpoint objects that you want to monitor. Informix Timeout: Specifies the threshold processing time of the checkpoint. If the processing time breaches the threshold, an alarm message is issued. checkpoint name > Checkpoint Query Config This section lets you view and configure the query properties that the checkpoint runs. Connection Name: Specifies the profile monitored connection. Condition: Defines the condition for evaluating thresholds. Checked Value: Retrieves the last measured value. Query File: Defines the file that stores the query. 16 Probe Guide for Informix Database Monitoring

17 informix Node Query: Defines the checkpoint read query. Interval Modus: Enables you to configure the interval value of the checkpoint. Note: The interval value is the difference between the results of two queries. checkpoint name > Row Identifier This section lets you pick the rows as variables to set an alarm message and suppression key. If the query returns more than one row, the Informix Database Monitoring probe needs a unique identification for each row. Note: This section appears only in custom checkpoints. checkpoint name > Message Variable This section lets you pick the columns as variables that are used in creating QoS. Data Type: Specifies the data type of the variable of the new alarm. Column Use: Specifies the column use of the variable. Note: This section appears only in custom checkpoints. checkpoint name > Exclude This section lets you view and configure the value of the exclude pattern column. checkpoint name > Include This section lets you view and configure the value of the include pattern column. Chapter 2: Configuration Details 17

18 informix Node Monitors Node The Monitors node lets you add and delete the Quality of Service definitions from the Informix Database Monitoring probe. Navigation: informix > Checkpoints > checkpoint name > Monitors Set or modify the following values as required: Monitors > Quality of Service This section lets you configure the QoS for the MySQL probe. Name: Defines the QoS name for SQL checkpoint. Metric: Defines a measuring value of the SQL checkpoint. Max value: Defines the threshold value for SQL checkpoint. Default: 1 Monitors > Threshold This section lets you configure the threshold values for the MySQL probe. Threshold object name: Defines the monitoring object name. Threshold value: Defines the value used for the threshold evaluation. Severity: Specifies the alarm severity. Message: Specifies the message name used for threshold alarm. Message text: Defines the message text. If the message name changes, the text is updated at run time. 18 Probe Guide for Informix Database Monitoring

19 informix Node Connection-<Connection Name> Node This node lets you configure the values required in the initial setup of the connection by the Informix Database Monitoring probe. Note: This node is user-configurable and is referred to as the Connection-connection name node in the document. Navigation: Checkpoints > Connection-connection name Set or modify the following values as required: Connection-connection name > Connection Setup This section lets you view the values required for the initial setup of the connection. Name: Defines the connection name. User ID: Provides user name for the SQL server or Windows authentication. Host Name: Defines the Informix Database Monitoring Server name/ip. DSN: Creates a DSN connection. In a DSN connection, only the DSN Name and password is required. DSN Name: Defines the ODBC DSN connection name. Protocol: Defines the connection protocol. Driver: Defines the connection driver. Service: Defines the connection service name. Server Name: Defines the connection server name. Database: Defines the database name. Chapter 2: Configuration Details 19

20 informix Node <Connection Name> Node This node lets you configure the connection properties. You can also define the threshold values related to the connection setup by the Informix Database Monitoring probe. Note: This node is user-configurable and is referred to as the connection name node in the document. Navigation: informix > Connection-connection name > connection name Set or modify the following values as required: connection name > Connection Setup This section lets you define the connection threshold properties. New Connection: Defines the new connection name. DSN: Creates a DSN connection. No other parameter is required except the password. Driver: Defines the driver name that the connection uses. Service: Defines the connection service name. Server Name: Defines the connection server name. Host Name: Defines the host name on which the connection runs. User ID: Defines the user name for SQL Server login authentication and Windows login authentication. Note: The user must have administrator rights on the informix database server. Database: Defines the database name for the connection. Timeout: Specifies the time duration for the probe before it aborts the connection. 20 Probe Guide for Informix Database Monitoring

21 informix Node <Profile Name> Node This node lets you define the properties of the profile which is created to monitor one instance of the connection. You can define different values for each profile related to each checkpoint. Note: This node is user-configurable and is referred to as the profile name node in the document. Navigation: informix > Connection-connection name > connection name > profile name Set or modify the following values as required: profile name > Profile This section lets you configure the properties of the profile. Active: Activates the profile. Default: Not Selected Heartbeat: Defines the interval at which all profile checkpoints schedules are tested and eventual checkpoint execution is triggered. Default: 5 Connection: Connection used in this profile. Check interval: Default value for the check interval in the profile. Default: 5 Check Interval Unit: Specifies the unit for the check interval. Clear message: Defines the message name for the timeout clear alarm. Profile Timeout: Specifies if the profile reaches the Profile timeout, the checkpoint processing is terminated. Default: 15 Profile Timeout Message: Specifies the message name used for threshold alarm. Timeout severity: Severity for timeout messages. Informix Timeout: Specifies the timeout set for breaking the connection with the server in case there is no activity. Alarm Source: Lets you override the source name of the alarm. Chapter 2: Configuration Details 21

22 Configure A Node Configure A Node This procedure provides the information to configure a particular section within a node. Each section within the node allows you to configure the properties of the Informix Database Monitoring probe. Follow these steps: 1. Select the appropriate navigation path. 2. Update the field information and click Save. The specified section of the Informix Database Monitoring probe is configured. Create Connection You can configure the probe to create a connection. Follow these steps: 1. Click Options next to the informix node in the navigation pane. 2. Click Create new connection. 3. Update the field information and click Submit. The new connection is saved under the informix node in the navigation pane. Add Profile Checkpoints You can configure the informix probe to add a checkpoint. Follow these steps: 1. Click the Options next to the profile name node in the navigation pane. 2. Click the Add Profile Checkpoints. 3. Update the field information and click Submit. The new checkpoint is saved under the Checkpoints node in the navigation pane. 22 Probe Guide for Informix Database Monitoring

23 Delete Connection Delete Connection You can delete an existing connection when you no longer want the Informix Database Monitoring probe to monitor it. Follow these steps: 1. Click the Options icon beside the Connection-connection name node that you want to delete. 2. Click the Delete connection option. The connection is deleted. Add Profile You can configure the probe to create a profile. Follow these steps: 1. Click the Options icon next to the Connection- connection name node in the navigation pane. 2. Click the Add profile option. 3. Update the field information and click Submit. The new profile is saved under the connection name node in the navigation pane. Delete Profile You can delete an existing profile when you no longer want the Informix Database Monitoring probe to monitor it. Follow these steps: 1. Click the Options icon beside the profile name node that you want to delete. 2. Click the Delete profile option. The profile is deleted. Chapter 2: Configuration Details 23

24

25 Chapter 3: QoS Threshold Metrics Many monitors ship with default QoS threshold values set. The default threshold values provide an idea of the type of values to be entered in the fields and are not necessarily recommended best practice values. To aid in tuning thresholds and reducing false-positive alarms, this section describes the QoS metrics and provides the default QoS thresholds. This section contains the following topics: QoS Metrics (see page 25) Alert Metrics Default Settings (see page 26) Checkpoints metrics (see page 28) QoS Metrics The following table describes the checkpoint metrics that can be configured using the Informix Database Monitoring probe. Monitor Name Units Description Versio n QOS_Informix_check_dbalive Availability Informix Availability 1.0 QOS_Informix_virtual_cpu_system Microseconds Informix virtual cpu system Time 1.0 QOS_Informix_virtual_cpu_user Microseconds QOS Informix virtual cpu user Time 1.0 QOS_Informix_user_locks users Informix Users Waiting For locks 1.0 QOS_Informix_table_size Megabytes Informix table size 1.0 QOS_Informix_table_extent Extents Informix Table Extents 1.0 QOS_Informix_buf_cachehit_ratio_write Percent Informix buffer cachehit ratio write 1.0 QOS_Informix_buf_cachehit_ratio_read Percent Informix buf cachehit ratio read 1.0 QOS_Informix_dbsize_size_mb MegaBytes Informix Dbspace Free Space MB 1.0 QOS_Informix_dbsize_size_pct percent Informix Dbspace Free Space Percent 1.0 QOS_Informix_dbsize_mirror_recovering status Database mirror recovery status 1.0 QOS_Informix_dbspace_mirror_offline status Database offline mirror status 1.0 QOS_Informix_dbspace_inconsistent status Database inconsistency status 1.0 Chapter 3: QoS Threshold Metrics 25

26 Alert Metrics Default Settings QOS_Informix_dbspace_recovering status Database offline status 1.0 QOS_Informix_dbspace_offline status Database offline status 1.0 QOS_Informix_active_users Users Informix active users 1.0 QOS_Informix_logging_status count Logging status 1.0 QOS_Informix_database_count Databases Informix database count 1.0 QOS_Informix_server_startup uptime Database Server Uptime 1.0 QOS_INFORMIX_chunk_io_ write writes Informix Chunk I/O Writes 1.0 QOS_INFORMIX_chunk_io_ read Reads Informix Chunk I/O Writes 1.0 QOS_INFORMIX_chunk_io_writes ChunkWrites Informix Chunk Writes 1.0 QOS_INFORMIX_lru_writes LRUWrites Informix LRU Writes 1.0 QOS_INFORMIX_foreground_writes ForegroundWrites Informix Foreground Writes 1.0 QOS_INFORMIX_deadlock_timeout deadlocktimeout Informix deadlock timeout 1.0 QOS_INFORMIX_deadlock_prevented deadlocksprevented Informixdeadlock Prevented 1.0 QOS_INFORMIX_checkpoint_wait checkpointwaits Informix checkpoint wait 1.0 QOS_INFORMIX_lock_wait LockWaits Informix lock waits 1.0 QOS_INFORMIX_buffer_wait BufferWaits Informix Buffer Waits 1.0 QOS_INFORMIX_latch_wait LatchWaits Informix Latch Waits 1.0 QOS_INFORMIX_lock_thread Transactions Informix Transactions Overflow 1.0 QOS_INFORMIX_lock_user Threads Informix Thread Overflow 1.0 QOS_INFORMIX_lock_session Locks Informix Lock Overflow 1.0 Alert Metrics Default Settings The following table describes the default settings for the informix metrics: Alert Metric Error Threshold Error Severity Description check_dbalive - Major Monitor connectivity to the database server server_startup - information Monitor the uptime (in days) of the database server database_count - information Monitor the number of databases 26 Probe Guide for Informix Database Monitoring

27 Alert Metrics Default Settings logging_status - information Monitor the logging status of the databases active_users - information Monitor the number of active users dbspace_offline - major Monitor databases for offline status dbspace_recovering - major Monitor if database is recovering dbspace_inconsistent - major Monitor if database is inconsistent dbspace_mirror_offline - major Monitor if database mirror is offline dbspace_mirror_recoveri ng - major Monitor if database mirror is recovering dbspace_size_pct - major Monitor dbspace free space (percent) dbspace_size_mb - major Monitor dbspace free space (MB) buf_cachehit_ratio_read - major Monitor buffer cache hit ratio for reads buf_cachehit_ratio_write - major Monitor buffer cache hit ratio for writes table_extents - major Monitor table extents table_size - major Monitor table size (MB) lock_session - major Monitor number of attempts to exceed the maximum number of locks lock_user - major Monitor number of attempts to exceed the maximum number of threads lock_thread - major Monitor number of failed attempts to allocate entries in the transaction table latch_wait - major Monitor number of times threads had to wait for a latch buffer_wait - major Monitor number of times threads had to wait for a buffer lock_wait - major Monitor number of times sessions had to wait for a lock checkpoint_wait - major Monitor number of times threads had to wait for critical section checkpoints deadlock_prevented - information Monitor number of times potential deadlocks are detected and prevented deadlock_timeout - major Monitor number of times distributed deadlock timeout is exceeded while user is waiting for lock foreground_writes - information Monitor number of foreground writes Chapter 3: QoS Threshold Metrics 27

28 Checkpoints metrics lru_writes - information Monitor number of LRU writes chunk_writes - information Monitor number of chunk writes user_locks - major Monitor number of users waiting for locks user_lock_wait - information Monitor users waiting for locks chunk_io_read - information Monitor chunk I/O read statistics chunk_io_write - information Monitor chunk I/O write statistics virtual_cpu_user - information Monitor virtual cpu user time virtual_cpu_system - information Monitor virtual cpu system time Checkpoints metrics The following types of checkpoint metrics are available for the informix probe: Count absolute number of events in the interval. In the first interval, counts are not checked because their interval value cannot be calculated. If there is a "total" value in the message, it means "since the start of the server". Count/sec absolute number of events in the interval per second. Count/sec is calculated as the difference between count at the beginning of the interval and at the end. The result is then divided by length of the interval. In the first interval, counts are not checked because their interval value cannot be calculated. If there is a "total" value in the message, it means "since the start of the server". Gauge absolute number, describing the actual state of the system. If it describes size, it is measured in KB or MB, depending on actual size. Ratio calculated percentage, using interval counts. In the first interval, it is calculated from total counts (as the interval count cannot be calculated). Status absolute value. Average calculated using interval counts. At the beginning of the interval, it is calculated from absolute counts. 28 Probe Guide for Informix Database Monitoring

29 Checkpoints metrics Single counter description The informix probe uses the following checkpoints: active_users: checks for current the probe users. buf_cachehit_ratio_read - ratio: Monitors buffer cache hit ratio for reads. Calculated as (1 - (disk reads/buffer reads)) * 100. buf_cachehit_ratio_write: Monitors buffer cache hit ratio for writes. Calculated as (1 - (disk writes/buffer writes)) * 100. buffer_wait: Monitors the number of times the threads had to wait for buffer. check_dbalive: This checkpoint tries to connect to a server. When the connection is not established, an alert is generated. This checkpoint cannot be deactivated. In case there is an alert, check the server connectivity or if the server itself is running. checkpoint_wait: Monitors the number of times the threads had to wait for critical section checkpoints. chunk_io_read: Monitors the read statistics for input/output in the chunk. chunk_io_write: Monitors the write statistics for input/output in the chunk. chunk_writes: Monitors the number of chunk writes. database_count: Monitors the number of databases. dbspace_count: Monitors the count of database space. dbspace_inconsistent: Monitors the database inconsistencies. dbspace_mirror_offline: Monitors the database mirrors for offline status. dbspace_mirror_recovering: Monitors the recovery status of the database mirrors. dbspace_offline: Monitors the database for offline status. dbspace_recovering: Monitors the database recovery. dbspace_size_mb: Monitors free database space in MB. dbspace_size_pct: Monitors free database space in percent. deadlock_prevented: Monitors the number of times potential deadlocks are detected and are prevented. deadlock_timeout: Monitors the number of times a distributed deadlock timeout is exceeded while the user is waiting for a lock release. foreground_writes: Monitors the number of foreground writes. latch_wait: Monitors the number of times a thread had to wait for a latch. lock_session: Monitors the number of attempts for exceeding the maximum number of locks. lock_thread: Monitors the number of failed attempts for allocating entries in the transaction table. Chapter 3: QoS Threshold Metrics 29

30 Checkpoints metrics lock_user: Monitors the number of user attempts for exceeding the maximum number of threads. lock_wait: Monitors the number of times the sessions has to wait for a lock release. logging_status: Monitors the logging status of the databases. lru_writes: Monitors the number of LRU writes. server_startup: Monitors the uptime of the database server (in days). table_extents: Monitors the extent of the tables. table_size - count: Measures the total table space size. user_lock_wait: Monitors the number of users waiting for locks. user_locks: provides a list of users holding a lock. The list helps in identifying users who are blocking other sessions (checkpoint locked_users). This checkpoint has default and count as threshold values. If the default threshold is set as 1, then the probe issues a message for every locked user with details about the user locking situation. If the default threshold is set greater than 1, then no message is issued. The count threshold defines the number of locked users as a threshold for this checkpoint. virtual_cpu_system: Monitors virtual cpu system time. virtual_cpu_usercheck_dbalive status: Monitors virtual cpu user time. 30 Probe Guide for Informix Database Monitoring